Daniel,
   Let me make sure I understand your proposal. Are you
saying that I should just strip out the symlinks in
%p/bin for the existing gcc4x packages and just create
a gcc4x-compiler package that depends on the appropriate
gcc4x package and provides these symlinks? This still will
cause some choas in the current packages since all of the
BuildDepends on gcc4x will have to be changed to gcc4x-compiler.
So there will have to be an upgrade process.
   I should be clear about my motivation for this. With
today's release of llvm 2.7, I was going to post
llvm-clang/llvm-gcc42/dragonegg-gcc packaging to fink
tracking. The dragonegg-gcc packaging is currently
problematic since it needs to both BuildDepends and
Depends on gcc45. This means that fink balks at
automatically replacing gcc45 with gcc44 whenever
dragonegg-gcc45 is installed. My aim was to allow
gcc44 and gcc45 to co-exist and then have dragonegg-gcc
use the compiler from /usr/lib/gcc4.x/bin/gcc.
           Jack
ps I am also strongly leaning towards adding the
-fsf-4.x suffix to the built compilers ala MacPorts.
This way the gcc4x packages can all present their
compilers in %p/bin without overlap. Also, there should
be a gcc 4.4.4 release in the next week or so such that
now would be a good time to address this issue as we
need to upgrade gcc44 anyway.

------------------------------------------------------------------------------
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to