The SVN repository is already usable. Currently it just contains: #in the root directory the trunk directory to hold the current development # version, a tags directory to tag versions and a directory for branches isaac@aaaabbbb:~/debian/pkg-octave$ ls branches tags trunk # in the packages directory, one directory for each source package we should # maintain, I've only added the octave2.1 package isaac@aaaabbbb:~/debian/pkg-octave/trunk/packages$ ls octave2.1 # and only the debian directory there isaac@aaaabbbb:~/debian/pkg-octave/trunk/packages/octave2.1$ ls debian # I've tagged the current octave2.1 version, so it's in the tags/ dir isaac@aaaabbbb:~/debian/pkg-octave/tags/packages/octave2.1$ ls octave2.1-2.1.64-3 #Every change should be done in the trunk directory, when we upload the #package to Debian we should also tag it. To tag it just run (there are other # ways): isaac@aaaabbbb:~/debian/pkg-octave/trunk/packages/$ svn copy octave2.1 ../../tags/packages/octave2.1/octave2.1-<package_version> # and then commit the change: cd ~/debian/pkg-octave/ svn ci # to add a new package to the trunk/packages directory just: apt-get source octave-forge (if you don't have it) cd octave-forge-<version> svn mkdir ~/debian/pkg-octave/trunk/packages/octave-forge/ cp -a debian ~/debian/pkg-octave/trunk/packages/octave-forge/ cd ~/debian/pkg-octave/trunk/packages svn ci # you should also create a tag for this initial version ------------------------------------------------------------- You should also be careful when creating the packages using the contents in the SVN to remove the .svn files before running dpkg-buildpackage, pbuilder or whatever. If you pass the -i option to dpkg-buildpackage it will get rid of the .svn files for you automatically. You can also run svn export instead of just copying the debian/ directory with the cp command. If you have any doubt about the SVN just ask. Best regards
Attachment:
pgpNhupXdli8N.pgp
Description: PGP signature