> On 30/10/13 11:08, Remi Mommsen wrote: > []> /opt/fink/bin/dpkg: error processing > /opt/fink/fink/dists/stable/main/binary-darwin-x86_64/languages/llvm-gcc42_2336.11-107_darwin-x86_64.deb > (--install): >> trying to overwrite `/opt/fink/bin/llvm-g++-4.2', which is also in package >> ccache-default >> /opt/fink/bin/dpkg-deb: subprocess paste killed by signal (Broken pipe: 13) > > When I reported this (in a thread on fink-beginners) a month ago, Jack's > answer was > >> ps The only solution that I see for llvm-gcc42 vs ccache is to have the two >> packages use >> update-alternatives in order to set symlinks to >> %p/bin/x86_64-apple-darwin13-*-4.2.1 for the >> %p/bin/llvm-*-4.2 files in the case of the llvm-gcc42 package controlling >> those symlinks >> and to %p/bin/ccache in case of the ccache-default controlling those >> symlinks. > > I don't know what the real solution will be, but IMHO u-a would only > make the situation more confusing. > > Meanwhile on 10.9, ccache doesn't build at all, because it wants to put > some "bin/*-apple-darwin*" symlinks into the -defaults splitoff. These > do not exist, because no corresponding files exist in /usr/bin, and > ccache-default builds differently depending on the presence of files in > /usr/bin. > > I think these symlinks should not be created in the InstallScript, but > at package installation time via a PostInstScript. This could then also > react to existing /sw/bin/llvm*4.2 executables.
When I inherited ccache, I was never really satisfied with the packaging of ccache-default, because it tries to provide symlink-wrappers to all possible compilers for any given distribution. There are two uses of ccache-default, for fink's builds, and for the user. I almost think that path-prefix-ccache would be more suitable for fink builds, than providing overrides directly in %p/bin. I am entirely open to suggestions. Fang -- David Fang http://www.csl.cornell.edu/~fang/ ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
