On Tue, Mar 22, 2005 at 09:03:40PM +0100, Martin Hejl wrote:
> >- - Re-target downloads to a local repository or mirror (to verify complete
> >independence from SF or leaf-project.org, and to control exactly which
> >version(s) of packages are used for an 'in-house' release). 
> That should actually be possible, at least for the packages we've 
> cleaned up already. Once everything is cleaned up, there should not be 
> any redundant server definitions - so changing the cvs-sourceforge 
> server definition in conf/sources.cfg to point to your mirror should 
> make every package definition use that mirror server (at least, where 
> cvs-sourceforge is used, and where we've removed all redundancies - if 
> you spot a package where this isn't the case, please let us know).
> 
> >- - Easily update a modified project to use new data from the SF CVS 
> >archives if/when it becomes available
> I presume you're referring to something like making changes to a 
> buildtool.mk file locally, and having upstream changes be merged into 
> your files upon request (just like it's done with conf/sources.cfg). 
> Unfortunately that's not possible (I've cursed that a couple of times 
> too), at least not within buildtool (since buildtool simply downloads 
> files via wget).
> What _is_ possible (even though it requires a little more manual work) 
> is to keep a checked out copy of our "apps" tree (where most of the 
> stuff comes from anyway), make changes there and then manually copy your 
> changes to buildtool/source/packagename/
> I admit it is cumbersome and somewhat error-prone, but that way one can 
> maintain local modifications and still benefit from upstream changes.

I don't know whether this information is useful, but I have done
something along the lines of above.

I have a local checkout of the cvs tree (buildtool and apps) and I
changed the sourceforge-cvs server in the buildtool config to direct
to my local apps checkout.

In this tree I have some local modifications to packages and also
added some packages of my own. This works without problems: I can use
the 'buildtool.pl build <package>' command and it "downloads" the
sources from my local cvs-checkout without any further configuration
or me having to make changes to sourced packages.

Furthermore I suppose that in this way you could also easily merge new
upstream versions with your locally modified sources. Only thing that
you have to think about then is, that you remove the "downloaded"
sources before you try to rebuild a package.

Jaap


-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click

_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to