hi all, I've been thinking about how to handle packages we create for us, and what to do with packages we derive from debian.
I'm leaning towards a structure like: packages-parkes mrconfig (incase we need one) galaxia-theme/debian debian-installer/debian linux-2.6/debian apt/debian otherpackagename/debian etc, and not carrying source for things in bzr. We'd need to make sure any package possible has a working get-orig-source script or target, but i think that is feasible, especially since a lot of stuff we free will be freed from debian anyway. if uscan can report out of date packages for us it'll be better then me forgetting to manually check as happens atm. What i've got locally to test this is an apt/ in bzr. $ cd srccache/packages-parkes/ $ ls total 8.0K drwxr-xr-x 3 kgoetz kgoetz 4.0K Jun 22 16:58 apt drwxr-xr-x 3 kgoetz kgoetz 4.0K Jun 22 19:01 cia-clients $ \ls apt/debian/gnewsense/ clean-upstream get-debian-source watch clean-upstream makes the changes needed for our freedom requirements, get-debian-source downloads the source and runs the clean script, and the watch file (standard format as used by debian) specifies where to get the source. Note that a script to clean its not necesary (but still desirable?), but we have to make sure whatever we are repacking is properly free before we ship it on :) I've not pushed that branch public as its still in the 'hm, could do this' stage, but any thoughts on the idea? kk -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian contributor / gNewSense Maintainer http://www.kgoetz.id.au No, I won't join your social networking group
signature.asc
Description: PGP signature
_______________________________________________ gNewSense-dev mailing list gNewSense-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/gnewsense-dev