From: Benjamin R. <ra...@be...> - 2005-04-22 14:38:07
|
why not take it a step further, and have the "gcc" and "g++" packages be part of a replacable package? ie: Package: system-gcc3.3 Provides: gcc3.3 Conflicts: system-gcc4, gcc4 Replaces: system-gcc4, gcc4 BuildDependsOnly: true Files: %p/lib/path-prefix/gcc %p/lib/path-prefix/g++ Package: system-gcc4 Provides: gcc4 Conflicts: system-gcc3.3, gcc4 Replaces: system-gcc3.3, gcc4 BuildDependsOnly: true Files: %p/lib/path-prefix/gcc %p/lib/path-prefix/g++ This would let a package just BuildDepends: gcc4 or gcc3.3 and get the Right Thing in it's path without any work. It also means the same info files would still work on 10.3 because we also have a "gcc4" package that could provide the same path-prefix files. I know there's details that wouldn't work exactly as I have it here, but the general idea would make things easier to transition, would it not? No need to override the path with gcc3.3 even when people are building with gcc_select set to 4.0, instead packages would BuildDepends on the right compiler, and if it's not specified, we can default to adding system-gcc3.3 to the builddepends. Thoughts? |