lenny bruce wrote: > At 11:57 PM +0200 8/25/02, Martin Costabel wrote: > >> Stephen Schafer wrote:
>>>>> [Stephen-Schafers-Computer:~] steve% startx -- -quartz >>>>> >>>>> 2002-08-25 16:28:16.516 XDarwin[551] No Info.plist file in >>>>> application bundle or no NSPrincipalClass in the Info.plist file, >>>>> exiting >>>>> giving up. [] >> You either need to get a newer package description, version 4.2.0-11 >> or higher, and recompile it, or get the missing files in XDarwin.app >> from some other source. > > No... I know what I'm doing and I have the same problem this guy has > exactly. > He's bungling the explanation because he doesn't know about necessary > details > like the environment settings and rc files... but that's not his problem. Excuse me, but do you also get the "No Info.plist in application bundle..." message? Unless you say yes, I don't believe you have the same problem as he. This message was typical for a crippled XDarwin.app built with April2002 or later dev tools and xfree86-rootless packages older than xfree86-base-4.2.0-11. The latest message from Stephen on 08/26 was that he recompiled version 4.2.0-12 and ran it successfully. I understand your frustration about things breaking with the Jaguar upgrade, but it doesn't help to lump all problems together and to suspect one big dark conspiracy responsible for all of them. It is much more useful to look at the problems in detail one by one. There are a couple of them, most of them are already identified (which does not mean they are all solved or even that a solution is known), and people are actively working on solving them. But the number of problems is much smaller than I had feared before upgrading to Jaguar. > I was doing just fine until I upgraded today to Jaguar... now XFree86 is > dead. I upgraded 4 quite different machines to Jaguar, and on all of them XFree86 is working just fine (and by an order of magnitude faster than on 10.1!). I recompiled xfree86 on all of them in the meantime using package descriptions from the new 10.2 tree, but even before that, the xfree86 fink packages that were compiled under 10.1 and quite a few of the other packages from 10.1 (even heavyweights like xemacs) continued to work almost without problems. There were some exceptions like xterm that no longer worked, but this was fixed by recompilation. There was no problem with OroborOSX, either. FinkCommander had some problems with Jaguar, but they are fixed in its current version 0.3.3a. > I even went as far as to remove my fink threaded versions (base/rootless) > and replace them with XonX's packages (XInstall/XFree86_4.2.0.1-10.2) > but it's the same bug... Which one precisely? > plus I now can't find an uninstall for XonX's Install[ed]Anywhere XFree86 > so I could try a rebuild with Fink Just rm the 3 directories /usr/X11R6, /etc/X11, and /Applications/XDarwin.app. > > plus Fink is really really really unstable and flaky under Jaguar > Fink Commander actually stalls out in places...I'm talking about Fink by > itself > (and yes I have the newest version of both and everything else too) > (and OroborOSX-0.8b2 doesn't work either) Not my experience at all. I did have problems with the Jaguar upgrades, but they were not related to fink. On one machine, the developer tools upgrade installed only half of its stuff, without any error message of course. Then the help viewer crashed always, as it turned out because of some incompatible old stuff in /Library/Documentation/Help. Running the new "Repair Disk Permissions" program from Utilities/Disk Utility showed dozens of permissions and ownerships that did not correspond to the new standard and had to be fixed. And so on. From what you are saying, I would rather suspect that your Jaguar upgrade has this kind of problems, too, and that they are responsible for what you are blaming on fink. > I've been following this guy's thread and it's not just him... it's me too. But he seems to be happy now... (Apart from some trivial problems with running a window manager). > and I thought I waited long enough for Jaguar to work with XFree86 > before I installed Jaguar... There are other applications that don't yet work with Jaguar, if this is any consolation. The poor guys from The MathWorks that wanted to ship the brand new $800 Matlab for MacOSX at about the same time Jaguar came out, for example, had to go back to their drawing boards and ask their customers to wait for several more weeks until a Jaguar-compatible version would be ready. Patience is the keyword here :-) -- Martin ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Fink-beginners mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-beginners
