Hi! On Thu, Aug 06, 2009 at 05:24:20PM +0200, Lucas Nussbaum wrote: > > This would require changing our procedures completely. I don't think > it's a good idea to do that now, and I don't see any clear advantage in > using git for managing our packages. I'd rather let another (less > understaffed) team with similar procedures experiment with git, and then > just copy what they did. >
the perl team was looking into this at debconf, not sure if people still are or not...but there's lots of interest in git in the perl team. > Switching to the layout that the perl team uses is a simple step that > has immediate benefits. > > Regarding -wip, I agree that all packages could reside in the same > directory. We just need a simple script to iterate over all packages > that are currently in the archive (easy to write). here's a script I use that basically does that: http://git.ryan52.info/?p=rebuild-scripts;a=blob;f=download;h=69a188de34d3159a45f972649a218ec0b48ba0f2;hb=HEAD so something like this should work: path=~/projects/deb/pkg-ruby-extras/trunk/ for i in $(find $path -mindepth 1 -maxdepth 1 -type d | sed 's/^.*\///' | grep -v "^.svn$" | grep -v ^tarballs$ | grep -v ^build-area$); do if grep -q "^Package: $i$" /var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_*_source_Sources; then echo $i; fi; done should probably change the _sid_ to _{sid,unstable}_ to account for different people's sources.list. Cheers, Ryan -- _________________________ Ryan Niebur [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
