On Thu, 2010-09-30 at 18:48 +0200, Enrico Weigelt wrote: > * Mike Noyes <mhno...@frontier.com> schrieb: > > > > ACK. IMHO we don't need tarballs at all. Just keep the complete > > > (uncompressed) trees in Git and selectively fetching them on-demand > > > (instead of a full clone). > > > > Enrico, > > We'll still need source tarballs for the SF FRS. > > Could be easily created on-the-fly or by a cron script. > > At least until the buildsystem is able to fetch directly via git. > > > > BTW: I'm keeping all sourcetrees and also the sysroot images > > > for my Briegel buildsystem [1] in git. Easier to manage and also > > > performs better than tarballs. > > > > I concur on this git structure. The problem is migrating our build tools > > to any new SCM. > > Of course. Perhaps you could explain the current process from > fetching the tarball (and maybe other files, eg. patches) until > the local source tree is set up and the actual package build begins > to me. I'll try to find a solution for a soft migration.
Enrico, Git is already enabled for our project. Would you like me to add you to our project, so you can assist us? https://sourceforge.net/apps/trac/sourceforge/wiki/Git git://leaf.git.sourceforge.net/gitroot/leaf/REPONAME (read-only) ssh://usern...@leaf.git.sourceforge.net/gitroot/leaf/REPONAME (read/write) -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
