Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Jun 2011 21:46:05 -0700
From:      Doug Barton <dougb@FreeBSD.org>
To:        Stephen Montgomery-Smith <stephen@missouri.edu>
Cc:        Stephen Montgomery-Smith <stephen@FreeBSD.org>, FreeBSD Ports <freebsd-ports@FreeBSD.org>
Subject:   Re: cvs commit: ports UPDATING
Message-ID:  <4E0D510D.7070305@FreeBSD.org>
In-Reply-To: <4E0D459B.9070808@missouri.edu>
References:  <201106302103.p5UL3heP028971@repoman.freebsd.org> <4E0D3D59.40800@FreeBSD.org> <4E0D459B.9070808@missouri.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On 06/30/2011 20:57, Stephen Montgomery-Smith wrote:
> 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,

Wouldn't be the first time. :)

> 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.

Ok, that's awesome!

> 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*.

Ok, so I guess we can store this idea for some time down the road when 
it's really needed.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E0D510D.7070305>