Hi on 23.05.2012 21:02, davidMbrooke wrote: > On Tue, 2012-05-22 at 23:10 +0200, Erich Titl wrote: >> on 22.05.2012 18:14, davidMbrooke wrote: >>> Hi all, >>> >>> I've noticed that we sometimes get conflicting updates to >>> conf/sources.cfg - especially when different developers add new Packages >>> at roughly the same time. >>> >>> One option to reduce this problem would be to change buildtool.pl to >>> automatically "include" every .cfg file in a specific directory. >>> The directory structure could look something like: >> >> I am not really clear why this would buy us anything, sources.cfg would >> still be a single instance. >> >> cheers >> >> Erich > > Hi Erich, > > I guess I didn't explain very well... > The "new" sources.cfg would not contain any <Source xyz> or <Package > xyz>definitions itself, just <Server xyz> entries and something like > <<include sources.d/*.cfg>> > > Then we'd have e.g. sources.d/busybox.cfg containing: > <Source busybox> > Server = localrepo > Revision = HEAD > Directory = busybox > Description = busybox > <Requires> > Name = buildenv > </Requires> > </Source> >
I got that much and personally I like the approach 2 things come to mind though 1) why would we still need a sources.cfg 2) contention would be less likely but not be done with. Still more than one developer might work on the same xyz.cfg. You certainly know about my bouts with GIT. I believe this is just a feature of distributed development. GIT is certainly trying to deal with this, but probably cannot handle one hundred percent. In the (real) old times, (SCCS, RCS...) a developer needed to lock a file before committing the changes. Not very modern, but effective. cheers Erich
smime.p7s
Description: S/MIME Kryptografische Unterschrift
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
