I was going to say, it would take some effort to backport the current egg repository to a given older version of Chicken. But I appreciate the new addition to chicken-setup; and at least I can create a Chicken 2.3 egg repository for the eggs I use.
-Ivan "felix winkelmann" <[EMAIL PROTECTED]> writes: > On 12/8/06, Peter Busser <[EMAIL PROTECTED]> wrote: >> Hi! >> >> On Thu, Dec 07, 2006 at 02:46:25PM -0800, Paulo Jabardo wrote: >> > I think that a simple solution, that would not solve this >> > particular problem but might help in the future is to have an egg >> > repository for each version. So if someone is using an older >> > version of chicken, the chicken-setup will use the appropriate >> > repository. However, new eggs wouldn't be available. >> >> Noone is keeping you from taking a snapshot of the current egg >>repository and providing support and fixes for old eggs. Please let >>me know when I can use this repository. > > That won't even be necessary. The current development version of > chicken-setup (darcs head, 2.509) can download from a SVN repository, > together with a given revision number. So if you need a specific version > of an egg, just do > > % chicken-setup -svn http://galinha.ucpel.tche.br/svn/chicken-eggs > -revision 2 ajax > > (of course this won'l help users of older chickens) > > Tagged eggs can be accessed with an URL that reflects the particular SVN tag > (which not all eggs provide). > > I have also added a "(required-chicken-version VERSION)" to chicken-setup. > > > cheers, > felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users