-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I had a user install fink on friday and upgrade to unstable I had to
fix it, but he may have used the binary installer, and the fix might
not be in that yet, not sure.
- ---
TS
http://southofheaven.org/
Chaos is the beginning and end, try dealing w
On Dec 5, 2006, at 11:03 AM, TheSin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> also on this topic, it's a long standing issue and I keep
> forgetting to mention it, but when you do the selfupdate from
> stable to unstable fink dies on gettext you ened to manually do
> fink
Doing a selfupdate automatically after reconfiguring to use unstable
would make sense, since users have to do that anyway if they're using
rsync updating. (and going the other way it would still be a good
idea)
On 12/5/06, David R. Morrison <[EMAIL PROTECTED]> wrote:
> That's great!
>
> I wonder
That's great!
I wonder whether, when a user has changed the Trees entry, fink
should automatically do a selfupdate at the end of 'fink configure'?
-- Dave
On Dec 5, 2006, at 12:30 AM, Daniel Macks wrote:
> As part of 'fink configure', HEAD now offers to enable/disable the
> "unstable" entr
As part of 'fink configure', HEAD now offers to enable/disable the
"unstable" entries in /sw/etc/fink.conf:Trees. Default is to leave
current settings unchanged. When enabling, the "unstable" analog of
each presently-enabled "stable" tree is appended to the Trees field.
Please test, fix wording of
