One of the side effects of fink-package-precedence is that /usr/local
becomes more of a visible problem. Well, it was always a problem, but
now it becomes a build-time crash rather than a silently-lurking
time-bomb). There are lots of legitimate reasons users may have
/usr/local stuff, but no good technical way to hide it from the
compiler.
We've previously considered and rejected the idea of *automatically*
moving /usr/local (or at least include/ and lib/) out of the way
during fink build operations because it's an "out of /sw" effect that
might affect other work the user is doing, and if the build fails, the
directories might not get put back in their original place.
Murr suggested a fink *option* to do it. I agree it's a nice feature.
Some ideas he and I kicked around include having fink warn if
/usr/local stuff is detected, and having a fink.conf opt-in control
that does the rename-while-build-then-restore. And vasi's "Finally"
feature (used by the BuildConflicts swappy and Buildlock removal
processes) to restore seems to provide a way to restore the moved dirs
even in most cases when the build fails. My only concern is for
parallel build operations ('fink build a' and 'fink build b' in
separate windows)...need to make sure the restore only happens when
*all* builds are finished, which may also not be the same build that
did the move originally.
So...thoughts about a boolean fink.conf:HideUsrLocal flag, where TRUE
means rename/restore and FALSE/UNDEFINED means issue warning?
dan
--
Daniel Macks
dma...@netspace.org
http://www.netspace.org/~dmacks
------------------------------------------------------------------------------
_______________________________________________
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
