On Tue, 13 Dec 2005 04:39:34 -0800, Steve Langasek said: > Just for reference, can you explain what it is that prevents the > library versions from being co-installable? I would expect a > mass-rebuild anyway, but it sends up warning flags for me to hear that > partial upgrades won't work. :)
The main reason is that the new version has some symbolic links where it used to be directories. e.g. to pick a directory at random, /usr/lib/GNUstep/System/Library/Images is now a symlink to /usr/share/GNUstep/Images, instead of being a directory in the old version. These symlinks are "owned" by the gnustep-make package, and so it will conflict with any packages that try to put stuff in the old directory locations. Actually, come to think of it, some of the libraries may be co-installable if I tighten up the dependencies a bit. (It seems like the packages that try to put things in the moved directories aren't the actual library packages -- just the "-common" packages.) I'll take another look at this. [...] >> The GNUstep-maintainer team's plan is to upload the new packages >> (once they're recompiled) first into experimental. Then, when we get >> the green light from -release, we will upload to sid. > If there are no conflicting transitions, is there any other reason to > upload to experimental first instead of uploading directly to > unstable? No, if there are no conflicting transitions, there isn't much reason to not go straight to unstable. The only other reason I can think of would be to give us some more testing of the migration before we hit unstable. If the other GNUstep maintainers have any comments on this, feel free to pipe in. -- Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
