From: Garrett Cooper on
On Sun, Apr 25, 2010 at 9:40 PM, Doug Barton <dougb(a)freebsd.org> wrote:
> On 04/25/10 17:15, Aristedes Maniatis wrote:
>> On 26/04/10 8:55 AM, Doug Barton wrote:
>>> I've just committed a fix for this problem to the svn (development)
>>> version of portmaster. You can find information on how to download it at
>>> http://dougbarton.us/portmaster-proposal.html. I would appreciate it if
>>> you would test that version in your environment to confirm that the fix
>>> is satisfactory.
>>
>> Firstly, it looks like it is unable to run with a relative path. Pretty
>> minor issue, but I thought I'd mention it.
>
> yes, there is no way that will work. portmaster calls itself
> recursively, so it has to have an explicit path when you start it.

_portmaster=$(realpath "$0")

?

....

"$_portmaster" foo

>> But when using an absolute path
>>     # sh /root/portmaster -ai
>
> You could also chmod a+x /root/portmaster and then run it without the
> sh, but the way you did it works fine too.
>
>> * I get the list of ports to upgrade, then "Proceed y/n", and after that
>> it sees CGatePro and tries to upgrade it.
>
> Yes, I was too hasty to get the fix out the door. I just committed
> version 207220 which has a more thorough fix for this issue in -a.
>
>> * when using portmaster -ai I'm still given a choice to upgrade the
>> package with no ORIGIN.
>
> I changed the logic for -a to be warn+skip automatically if an +IGNOREME
> file is present. For the case of no ORIGIN and no +IGNOREME it's back to
> being a fatal error.
>
>> But why ask since we already know it will fail 100% of the time?
>
> Exactly right.

Thanks,
-Garrett
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"