?

Log in

No account? Create an account

Previous Entry | Next Entry

mkdir -p ~/rpm/{SPECS,SOURCES,BUILD,RPMS,SRPMS}
mkdir ~/rpm/{SPECS,SOURCES}/CVS
echo ':pserver:cvs@cvs.pld-linux.org:/cvsroot' > ~/rpm/SPECS/CVS/Root
echo ':pserver:cvs@cvs.pld-linux.org:/cvsroot' > ~/rpm/SOURCES/CVS/Root
touch ~/rpm/{SPECS,SOURCES}/CVS/Entries
echo 'SPECS' > ~/rpm/SPECS/CVS/Repository
echo 'SOURCES' > ~/rpm/SOURCES/CVS/Repository
poldek -i cvs rpm-build
cd ~/rpm/SPECS
cvs up builder
./builder yourpackagename

If you want the whole SPECS tree, run cvs up in the SPECS directory, and it'll download the ten thousand-odd spec files.

If you make changes, run the ./adapter script on the spec to check for sylistic glitches. Make sure that adapter is sane, though, since it can be over-aggressive. If the changes are generally useful, send the new spec (or better, a diff — one can be made with cvs diff file.spec) to the PLD developer's list

Comments

( 2 comments — Leave a comment )
didzej1
Jul. 24th, 2005 02:21 pm (UTC)
another tip
If you insert

%_topdir %(cd ..; pwd)

into your ~/.rpmmacros you can have the rpm subdirectory in any directory you can think of, not just in $HOME.
Just my $0.02 :)
aredridel
Aug. 30th, 2005 12:49 am (UTC)
Re: another tip
Sweet! That actually solved a problem of mine working with a separate DEVEL branch tree.
( 2 comments — Leave a comment )