On Sunday, August 24, 2003, at 04:15 PM, Benjamin Reed wrote:
Please chill out, it's called unstable for a reason. I made a
mistake, I will fix it when I have more than 3 minutes at a time to
dig into weird packaging dep issues. In the meantime, this is a valid
workaround.
Well, the only re
On Sunday, August 24, 2003, at 7:02 PM, Martin Costabel wrote:
Ben Hines wrote:
Telling every fink user to do this is idiotic.
Why do you write this to me? I complained to the maintainer
immediately when this came out (*), but although I can imagine several
solutions of the problem myself, I'll
Ben Hines wrote:
Telling every fink user to do this is idiotic.
Why do you write this to me? I complained to the maintainer immediately
when this came out (*), but although I can imagine several solutions of
the problem myself, I'll leave it to him to fix it. In the meantime, I
will go on helpi
A quick workaround might be to have an "upgrade-system-xfree86" package
that installs a shell script to do the uninstallation--similarly to how
that for XFree86-4.2 -> XFree86-4.3 was done.
I've put up a FAQ entry, but didn't want to overstep my bounds by
editing the news.
--
Alexander K. Hansen
Telling every fink user to do this is idiotic. If that is the plan, it
should obviously be posted as a news item AND put in the FAQ.
Things like this are why people complain about fink, because there are
always errors, always problems, never simple updates. It doesn't 'just
work' - every few m
Pascal Bourguignon <[EMAIL PROTECTED]> wrote:
[snip]
> With the CVS HEAD it seems that clisp/configure does not take into
> account the CC environment variable: It's still using 'gcc', while in
> by script, I explicitely set export CC=3D'cc -no-cpp-precomp'.
> Obviously, since it's s
I'm actually a little confused as to why each *package* needs the gcc:
3.1 | 3.3 flags. Its only important to which version of gcc3 we
compile
with, not which code we compile.
Shouldn't fink just keep track of which gcc3 a given package was
compiled with instead of making a duplicate info file for
> * In message <[EMAIL PROTECTED]>
> * On the subject of "Re: Compiling CLISP on MacOSX"
> * Sent on Sat, 23 Aug 2003 16:40:33 +0200
> * Honorable Pascal Bourguignon <[EMAIL PROTECTED]> writes:
>
> With the CVS HEAD it seems that clisp/configure does not take into
> account the CC environment varia
