Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 May 2008 10:01:36 -0600
From:      Tim Judd <tajudd@gmail.com>
To:        Gilles <gilles.ganault@free.fr>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Is it safe to upgrade libraries?
Message-ID:  <1211817696.1154.3.camel@t60.local.zz>
In-Reply-To: <r3cl34deq33946dlq9ff8dsr0fv7qj1112@4ax.com>
References:  <r3cl34deq33946dlq9ff8dsr0fv7qj1112@4ax.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mon, 2008-05-26 at 14:47 +0200, Gilles wrote:
> Hello
> 
> When running "'pkg_version -v", I notice that some libraries are out
> of date, such as the most important glib:
> 
> glib-2.14.6                         <   needs updating (port has
> 2.16.3)
> 
> Before I go ahead and run "cd /usr/ports/devel/glib20 ; make ; make
> install", I'd like to check what the recommended way is to upgrade
> critical applications like this?
> 
> As I connect remotely through SSH, I wouldn't want to break this box
> and have to drive to the location because it won't run after the
> upgrade.
> 
> Thank you.
> 

I think of it this way --

since ssh is part of base -- which doesn't need your glib to run --
connecting by ssh to upgrade that should be fine, since you're not
changing something that's "in-use".

Second of all, after you actually connect to a ssh session, the session
you're using has the program and libraries in ram, and you can swap out
anything you want while you stay connected.  Programs that use the
affected library should be restarted for changes to take effect.

I have no hesitation that upgrading PORTS/PACKAGES over ssh will cause
problems.  You might need to restart some services (think of a nss or
pam plugin that alows you to authenticate over say LDAP or samba or
SQL).


I have more hesitation when I do a system upgrade than when I upgrade
ports/packages.

Hope this helps.

--Tim




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