upgrading installed ports: time to do it ?

[Chris Whitehouse]

dan wrote:
> On Tuesday 23 June 2009 23:21:21 Chris Whitehouse wrote:
>> RW wrote:
>>> On Mon, 22 Jun 2009 20:58:41 +0100
>>>
>>> Chris Whitehouse <cwhiteh at onetel.com> wrote:
>>>> I'll probably get flamed for this but since I've been using
>>>> ports-mgmt/portmanager I've almost forgotten
>>>> about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it
>>>> was. I've upgraded ports just by doing 'portmanager -u' over one or
>>>> two quite major changes and not had any problems that haven't been
>>>> down to an individual ports.
>>> You still need to read UPDATING, portmanager handles some of the
>>> issues automatically, but not all.
>> Not trolling but can you give me some examples?
>>
>> Chris
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at freebsd.org"
> 
> Yes. I think there is at least one. Please, consider to correct me if I am 
> wrong.
> 
> Yesterday, reading the contents of /usr/src/UPDATING in the source tree (using 
> portupdate-scan) I found :
> 
> "[...]
> 20090608:
>   AFFECTS: users of lang/python* and py-*
>   AUTHOR: miwi at FreeBSD.org
> 
>   The default version of Python has been changed from 2.5.x to 2.6.x.
>   If you have 2.5.x installed, perform an upgrade of lang/python25 to
>   lang/python26 with the following command:
> [...]
> "
> Can portmanager know that the default version of a port has been changed and 
> then you need to do the upgrade to the newer major version ?

I don't know. I will put testing it on my todo list (which I really do 
hope to get around to :)

Chris

> 
> And if it can  know that... can also portmanager know that 
> 
> "[...]
> Once the installed Python has been updated to 2.6, by using the
>   method above, it is required to run the upgrade-site-packages target in
>   lang/python to assure that site-packages are made available to the new 
> Python
>   version.
> 
>  [...]   "?
> 
> If, otherwise, using portmanager you end up with a newer version of python 2.5 
> (for example)... are you sure that every upgrade in the future will work 
> flawlessly ? After Reading the UPDATING file a guy will
> "
> [...]   set the   PYTHON_DEFAULT_VERSION variable to 'python2.5' without 
> quotes in  make.conf, then go to lang/python and perform the following
>   command:
> [...]
> "
> will portmanager do the same ?
> 
> 
> d
> 
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>