On Sunday, August 17, 2003, at 12:49PM, Martin Costabel wrote:

I guess one first has to force-remove the old system-xfree86 before upgrading? Otherwise one gets

system-xfree86 conflicts with x11
system-xfree86-43 provides x11 and is to be installed.
dpkg: error processing /sw/fink/dists/unstable/main/binary-darwin-powerpc/x11-system/system- xfree86-43_4.3-1_darwin-powerpc.deb (--install):
conflicting packages - not installing system-xfree86-43

Hmm... Did you do an upgrade (or install system-xfree86) or did you just install system-xfree86-43 directly?


There's a new system-xfree86 that doesn't conflict with anything but depends on either system-xfree86-42 or system-xfree86-43, I thought it had a clean upgrade path but I made these packages a month ago so I could be mistaken.

I'll do a little digging...

Another problem is that this package doesn't like it if you first installed Apple's X11 and then a non-Apple xfree86. If it finds /usr/lib/libXplugin.1.dylib but not /usr/X11R6/bin/Xquartz, it tells you you have a partial Apple installation and refuses to install. So you need to remove not only /usr/X11R6 and /etc/X11, but also /usr/lib/libXplugin.1.dylib.

Well, that's because you do have things mixed up. =)


I can make it error out more cleanly, perhaps (and give suggestions), but having those things could possibly confuse things.

In my - special - case, this is not an option, because I am trying xfree86-4.3.99.10 from cvs which ATM needs libXplugin and doesn't build Xquartz, so I am obliged to cheat anyway. No big deal.

An option for cheating would be nice, however: Instead of failing, it could tell that it thinks the X11 installation is rotten and then ask what one wants to do

Well, the real fix is for system-xfree86-43 to handle the case of the 4.3 snapshots nicely (by checking the version, and accepting the combination of libXplugin.1.dylib and no Xquartz). I hadn't realized 4.3.99 changed that. I'll make that change as well.


--
We put a lot of thought into our defaults.  We like them.  If we
didn't, we would have made something else be the default.  So keep
your cotton-pickin' hands off our defaults.  Don't touch.  Consider
them mandatory.  "Mandatory defaults" has a nice ring to it.



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to