On Fri, May 23, 2008 at 3:15 PM, Christopher Arndt <[EMAIL PROTECTED]> wrote: > > Hi all, > > I was wondering whether it would be useful to host our own vendor > branches [1] of Pylons and webhelpers, since there is is still no > released version of these projects that supports the current TG2 trunk. > to be honest I'll prefer to push for the release.
> When we want, for example, to provide our own custom eggs for Pylons and > webhelpers via something like EggBasket [2], it would be useful to have > a repository from which these eggs could be built, where we know that > the current state works with TG2. > that said this is easy, see below. > I am not sure, though, if the concept of vendor branches is not already > covered by mercurial's distributed approach. If so, I would be glad if > somebody could explain to me, how this could work. > well that's one of the nice things of dvcs since each branch is just another repo a vendor branch here will be just a read-only repo, that will live in TG's server from which you will only pull changes from pylons tip. and all TG's intructions and egg will come out of that TG hosted pylons repo. This way you could have an "oficial" unofficial pylons dist to serve TGs needs. > Just an idea that came up in during discussions with my Gsoc student > regarding building eggs for TG2 dependencies. Any comments appreciated. > > Chris > > [1] http://svnbook.red-bean.com/en/1.4/svn.advanced.vendorbr.html > [2] http://pypi.python.org/pypi/EggBasket > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
