On Tuesday, September 3, 2002, at 09:21  AM, Ronald Florence wrote:

>
> On Tuesday, September 3, 2002, at 11:52  AM, Adrian Simmons wrote:
>
>> If you have everything set up now (read the manual? done 'fink 
>> confgure'?), then you should just be able to do 'fink install gimp'.
>
> It appears that this will only work if I move the unstable/main and 
> unstable/crypto trees into my default (10.2) configuration.  If I do 
> that, and try `fink update-all' it appears that fink wants to install 
> xfree86-rootless' -- which I fear will trash my XDarwin installation.
>

Why do you think it would trash your XDarwin installation? If you have 
a manual install of XDarwin (not thorough fink) just install 
system-xfree86. If it doesn't give you that option, it is a bug, let us 
know where that happens. Please.


> I feel like I've gotten onto a descending spiral.  All I wanted was a 
> working gimp, and I've done a series of upgrades to fink which now 
> leaves the fink installation in a situation that threatens to unravel 
> previous installations of important software packages.
>

What part of "if you are willing to test our experimental version of 
fink" was hard to understand?

> If the stable 10.2 tree isn't ready yet --  which I can certainly 
> understand, given the newness of 10.2 -- perhaps I should wait a while 
> before trying to install and configure gimp.  This is a working 
> machine, and I can't afford to see XDarwin  or other basic utilities 
> trashed.

So you really aren't willing to help us test the upgrade? Then you 
should have said so - I wouldn't have explained how to try the 
experimental fink, rather I would have told you to wait.

-Ben



-------------------------------------------------------
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-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to