/usr/ports/UPDATING - change command

Jeremy Messenger mezz7 at cox.net
Wed Jul 2 15:31:10 UTC 2008


On Wed, 02 Jul 2008 10:21:30 -0500, Jeremy Messenger <mezz7 at cox.net> wrote:

> On Wed, 02 Jul 2008 09:42:05 -0500, Ross Gohlke <ross at grinz.com> wrote:
>
>>> 20080630:
>>>   AFFECTS: users of graphics/poppler* and future users of firefox3
>>>   AUTHOR: FreeBSD GNOME Team <gnome at FreeBSD.org>
>>>
>>>   The poppler* ports have been updated to 0.8.3 and the shared  
>>> libraries
>>>   have changed.  Firefox 3.0 has been added to the tree as  
>>> www/firefox3.
>>>   These changes require that all dependent ports be updated.  You can  
>>> do
>>>   this in one of two ways:
>>>
>>>   # portmaster -a
>>>
>>>   or
>>>
>>>   # portupgrade -a
>> I propose the following change VVVV
>>
>> These changes require that any port which depends on any poppler* port  
>> must be upgraded. For each poppler* port installed:
>> <I don't use portmaster>
>> or
>> # portupgrade -rf <poppler-port-name>
>>
>> You can see what would happen first with:
>> # portupgrade -rfn <poppler-port-name>
>>
>> ----------------
>>
>> Unless I'm missing something, portupgrade -a is completely unnecessary  
>> and in my case would be dangerous.
>
> The 'port* -a' aren't dangerous if you follow every steps in UPDATING.  
> The 90% of bug reports that we get because users don't have installed  
> ports up to date.

Umm... 'every steps'... It could be problem for anything above than  
poppler/firefox. I will tweaking in UPDATING. I just need to think for  
firefox3 too.

Cheers,
Mezz

> Cheers,
> Mezz


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org


More information about the freebsd-gnome mailing list