Hello all, since porting apps to guile2 has been pretty painful so far, I decided to take another try. My take so far has been to create a new package called guile2. This will allow for the new packages that depend on guile2 to be built, while the old stuff won't be broken because guile1.8 will still be around. What would be the preffered way to proceed? I think the best way is to leave one version (likely guile2?) as the default and rename the binaries and some other conflicting files in the old package. I can also rename the original guile to something like guile1.8 and update the original content with guile2 stuff, but IMO that is pretty cumbersome. Some problems I've encountered: * Multiple info files. I suggest keeping only those in the new package and remove them from the old one. * Both packages contain guile.m4. This is the only problem I'm not sure how to solve yet. Both packages also contain guile-config that can be called by one of the autotools macros. I guess that renaming that file in both packages and symlinking it from the default package would be ok in theory, but that still doesn't solve the problem with the m4 files. Any thoughts? Anyway, you can find the packages here [1]. They should be installable and runnable in parallel with guile. These are not meant to be final in any way, just to demonstrate that it would be quite possible to have both of them in the system. Thoughts and feedback appreciated. [1] http://jsynacek.fedorapeople.org/guile/pkgs/ Cheers, -- Jan Synacek Software Engineer, BaseOS team Brno, Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
