[Mageia-dev] Distributed packaging for a community distro

Sun Sep 19 15:05:24 CEST 2010

'Twas brillig, and Aurelien Bompard at 19/09/10 12:52 did gyre and gimble:
+>>  * Binary churn: If we add the tarballs, there can be a lot of binary
+>> churn. Cloning a git repo means we get the full history locally which
+>> means all copies of the tarball over the x years period. SVN is better
+>> suited to binary churn, only keeping the most recent version in your
+>> checkout. This is likely discussed above.
+> 
+> In Fedora, the tarballs are kept on a separate server, and a "sources" file 
+> with SHA1 sums is included in the git repo. The "fedpkg" tool can upload 
+> tarballs to the cache.
+
+Perfect.
+
+>>  * Tagging: When a release is done, the packages need to be tagged. This
+>> is more awkward with individual repos rather than one central one, but I
+>> suspect it's a relatively easy process to script.
+> 
+> AFAIK, there's no global tagging for a release in Fedora.
+
+That's certainly one way to solve that problem :p
+
+Cheers
+
+Col
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+