Hi Charles, > This is where subversion's branching would really shine. You would > simply change the repository URL in the main config file and 'head' > would point to the latest version of that branch, which is probably what > you'd want (ie: security updates/bug fixes included). Ah, ok, I get it. Thanks for the clarification.
> You would have the same problems the current CVS version has with > versions if you wanted to build to a particular repository version > number, rather than the latest version of a branch/tag, however. Right. > Ideally, building from a local working-copy of the repository will be > fairly easy (it sounds like this is getting tested RealSoonNow). This > would separate download problems from actually building the source > (possibly important for those with flaky internet access, or folks using > the flaky sourceforge CVS servers! :). Well, that's what the whole "we supply a tarball of everything you need, and put it into FRS" approach was all about. But it seems that is not an approved approach. > This would also somewhat isolate > buildtool from the actual download mechanism, making it possible to use > subversion, bit-keeper, perforce, or whatever should anyone want to. It > would also mean buildtool wouldn't have to be updated to support > building arbitrary versions...you could select from one (or a few) major > revisions and get automatic downloads/builds by adjusting the repository > URL, and manually create a working copy to build from if you wanted some > arbitrary version of a package (or packages) for some reason. I don't disagree with any of that, but you need to see it from my point of view. I do not have the time to make that migration, and to me, building old sources is not a priority (I already can do that for the old packages I need to support, because I have backups of my old buildenvs stashed away somewhere). So, to me, the whole thing would mean spending time I don't have on something that lets me do things I can already do. Now, believe me, I surely understand that there's more to software development than doing just the "cool stuff" that one is interested in - but since that pretty much sums up my day at work, I'll opt to not do so in my evenings as well, at least for something I don't consider to be something critical. I'm not going to debate the fact that it would surely be nice if somebody did it though > I have briefly looked at the buildtool source in CVS, and it looks like > it would be pretty simple to add a subversion download method. If I get > some spare time I may try to do this, although I'm not exactly a perl guru. You are very welcome to try (and don't hesitate to ask if you run into trouble - at leat, the "non-subversion" kind of trouble ;-)) - I just don't have the time to do the work (and worse, the testing - doing a fresh checkout of everything and a rebuild uses up a whole evening on my internet connection/build environment). Martin _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
