ACSpike:
mental@...3... wrote:
Personally, I'd not invite pain by bypassing the package system so lightly. ^_-
mental has a point there. OTOH, this will then come up again the next time we need a library version where no deb exists.
Yeah I was afraid of installing to /usr on my nice new clean system. But I installed to /usr/local, edited /etc/ld.so.conf and ran ldconfig. That made things work (or seems to have made things work -- I'm still waiting for it to finish compiling). The reason I was building my own libgc is that Mike suggested I build libgc with apbuild for portability reasons. What are the pros/cons of what I have done?
Con: 1. Some packages don't support make uninstall. 2. You also might miss patches specific to your system applied by the deb providers (rarely needed but nevertheless).
Pro: You can fiddle with the source. One example would be building profiled versions of packages to look for performance bottlenecks. Etc. You have CONTROL, finally.
A workaround would be to build a package from the source specs (if existent) then install the package with dpkg. As this does not address Con 2, you would need the diffs provided by debian.org that they apply to the sources. But that's all and not too bad, given that most source packages have specs now.
ralf