On 06/30/2011 10:22 PM, Doug Barton wrote:
On 06/30/2011 14:03, Stephen Montgomery-Smith wrote:
stephen 2011-06-30 21:03:43 UTC
FreeBSD ports repository
Modified files:
. UPDATING
Log:
- Tell octave-forge* users to completely remove old ports before
reinstalling.
This is not the first time this issue (ports doing the wrong thing if
you try to build them while they are installed) has come up, and I've
been thinking ... do we need something like a NO_REINSTALL flag that can
be added to a port's Makefile to indicate the problem? I realize that in
many cases the problem is better solved by fixing the real problem.
However I think that there are likely situations like this where there
is a legitimate problem that can only be overcome by removing the
installed ports first.
Is this idea worth pursuing? I have some ideas about how it should be
implemented but I'm curious what others think about the concept first.
Doug
Doug,
I just wanted to say that you may have misunderstood my commit log,
because of some personal email exchanges we have had. I have now
repaired the octave-forge ports so that there is no need to have them
use a NO_REINSTALL flag. However, this required me to redesign how the
ports work. So my message in UPDATING was merely telling the users to
deinstall all the octave forge ports ONE TIME, before rebuilding them.
After deinstalling them and then reinstalling them, the octave-forge
ports should afterwards be completely compatible with portmaster.
So a NO_REINSTALL flag is not required for octave-forge*.
(Not that other ports might need it.)
Thanks, Stephen
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
