Dave,
Why remove the gc package when you could just add a BuildDepends
on cctools (>= 622-1)? Actually, if more packages had such dependencies
it might help accelerate the addition of an Xcode virtual package
to fink (to make the relationship between a particular cctools package
and Xcode versio
That's too bad... if gc gets dropped, won't this cause trouble for
packages depending on gc, like inkscape? I guess one could keep a
legacy version of gc that is known to work.
Jens
On Jul 21, 2007, at 9:53 AM, David R. Morrison wrote:
> In addition to this XCode issue, I've received a few
In addition to this XCode issue, I've received a few private bug
reports about the new gc package. If I can't resolve them soon, I
may remove the package from fink.
-- Dave
On Jul 19, 2007, at 3:05 PM, Jens Noeckel wrote:
> Hi,
>
> gc (7.0-1001) compiles fine with XCode 2.4 on an Intel
I propose that ruby16 join the list of obsolete versions of language
packages that we won't support in 10.5. (The others already on this
list are perl581, perl581, python23, and java13.) We would retain
ruby 18.
Does anybody forsee any problems with this?
-- Dave
