On Tue, 09 Sep 2014 16:29:21 +0200 (CEST) Felix Winkelmann <felix.winkelm...@bevuta.com> wrote:
>> Assuming egg authors won't create new repositories for their eggs for >> CHICKEN 5, the henrietta-cache instance for CHICKEN 5 would still cache >> versions that are only compatible with CHICKEN 4, although they will be >> only meant to be used by CHICKEN 5. I think that's not a really serious >> issue, but I thought it should be mentioned, just in case somebody tries >> "chicken-install5 <egg>:<version-for-chicken-4>". We can work around >> that by providing .release-info files specific to CHICKEN 5 (e.g., in a >> chicken-5 branch), containing the versions compatible with CHICKEN 5 >> only. Maybe there are better options? > > Well, the problem are eggs that are not in our central repository. I think the versioning thing also affects the eggs in svn too. For example, suppose right now you have egg foo at version 1.0. When CHICKEN 5 is released, foo will be ported to CHICKEN 5. What version will it be in CHICKEN 4 and 5? After we have the egg for both CHICKEN 4 and 5, how to manage new versions? I'm quite sure we have a solution for this problem, which is basically the same as we had in the CHICKEN 3->4 transition. Unfortunately, since I was the last person I know to switch to CHICKEN 4, I didn't actually faced that problem with my eggs. Since nobody else was using CHICKEN 3, I just froze egg versions for that CHICKEN version and continued to update eggs for CHICKEN 4 only. > There must be a way to mark for which versions an egg is > intended. That's why I propose another entry in the .release-info > files. Another alternative would be using another .release-info file. That approach wouldn't require changes in henrietta-cache. For example, we'd have https://raw.github.com/mario-goulart/awful/master/awful.release-info for CHICKEN 4, and https://raw.github.com/mario-goulart/awful/chicken-5/awful.release-info or https://raw.github.com/mario-goulart/awful/master/awful.release-info.5 for CHICKEN 5. Of course, other variations are possible. It'd be just a matter of pointing to a CHICKEN 5-specific .release-info. Best wishes. Mario -- http://parenteses.org/mario _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers