We do that, except that we have current as an alias to the 2.0b1 directory at the moment.
That way we don't constantly have to change the install instructions. I was thinking about this last night and perhaps what we need is to 1) include the latest setuptools in our index 2) create a /development index that's got the eggs needed to run the dev version Ideally the /dev version would be automatically updated whenever the automated tests pass on buildbot. --Mark Ramm On Wed, Jan 14, 2009 at 5:11 AM, Diez B. Roggisch <[email protected]> wrote: > On Wednesday 14 January 2009 07:03:07 Mark Ramm wrote: >> But without it: >> >> python setup.py install >> >> may not work because who knows what versions of what libraries you can get. >> >> Setuptools is terrible, but it's what we've got. >> >> I'm flexible on what we should do here, but I don't know if there is >> any right way to do it. > > How about you keep the index-pages around, named/numbered? This is what we do > with eggbasket versionsets, and it works. > > All you do is you > > - create a new versionset (you do that manually right now) > - alter setup.cfg to point to that > - commit setup.cfg > > That will constrain a specific version to it's matching set. If the user > updates via SVN, he'll get the new versionset. If not, the versions stay > frozen. > > Diez > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
