Re: Question about updating packages

[Marc Espie]

On Mon, Mar 20, 2017 at 08:57:42PM -0500, mitchell wodach wrote:
> Someone correct me if I'm wrong but wouldn't you want to pkg_add -Uu. Which
> updates dependent packages also?

Nope.

pkg_add -U  exists for when you want to install a package in a hurry,
and don't want to update your whole base of installed packages (roughly
500 packages on my current laptop)

Saved our collective asses lots of time, say you run current, realize you
forgot to install magicpoint, and do a pkg_add magicpoint... figure out 
nothing matches, decide to do a pkg_add -u first, and then wait for 2 hours
until you updated the whole of texlive and the rest of your system.

So, this is exactly how pkg_add -U was born, and the scenario becomes
pkg_add -U magicpoint
which will only update the dependency tree leading to magicpoint (e.g.,
freetype), then install magicpoint and let you get a shiny new magicpoint 
in about 1 minute, knowing full well, you will reserve a few hours to 
get texlive updated later.

Re: Question about updating packages

[Thomas Weinbrenner]

On Mon, Mar 20, 2017 at 08:57:42PM -0500, mitchell wodach wrote:
> Someone correct me if I'm wrong but wouldn't you want to pkg_add -Uu. Which
> updates dependent packages also?

Not necessary if he uses pkg_add -u to update ALL packages.

pkg_add -u $PACKAGE   -> updates $PACKAGE
pkg_add -Uu $PACKAGE  -> updates $PACKAGE and dependencies
pkg_add -u-> updates all packages

Question about updating packages

[mitchell wodach]

Someone correct me if I'm wrong but wouldn't you want to pkg_add -Uu. Which
updates dependent packages also?

On Mar 20, 2017 8:52 PM, "Jordon"  wrote:

>
> > On Mar 20, 2017, at 8:47 PM, Michael McConville 
> wrote:
> >
> > Jordon wrote:
> >> I have current running on some machines and multiple times a week I
> >> will update them by booting bsd.rd and doing the (u) option (i think
> >> that is the ‘proper’ way to update to the latest current base system).
> >>
> >> I will occasionally update all the packages I have installed by doing
> >> a ‘pkg_add -u’ as root.  Based on the output, it is going through the
> >> packages, checking for newer versions, and updating if there is one.
> >> It then prints a “pkgname-oldver->newver” string.  The thing is, a lot
> >> of the time the old version and new version is the same.  What does
> >> this mean?  A slight tweak to a makefile or something that wasn’t
> >> significant enough to rev the version number?  Some date discrepancy
> >> with the mirror i am pulling it from?  I know it’s a small thing, but
> >> it really has me puzzled.
> >
> > It typically means that one of the libraries that the package depends on
> > has been updated. This can be either a system library (included in the
> > base system) or a third-party library (installed as a package). Because
> > its dependencies are updated, the binary has to be relinked.
> >
> > For what it's worth, this is also why you will see warnings like the one
> > below if you run a binary that is out-of-sync with your libraries:
> >
> >> WARNING: symbol(foo) size mismatch, relink your program
>
>
> Thanks!  That makes sense.
>
> Jordon
>
>

Re: Question about updating packages

[Jordon]

> On Mar 20, 2017, at 8:47 PM, Michael McConville  wrote:
> 
> Jordon wrote:
>> I have current running on some machines and multiple times a week I
>> will update them by booting bsd.rd and doing the (u) option (i think
>> that is the ‘proper’ way to update to the latest current base system).
>> 
>> I will occasionally update all the packages I have installed by doing
>> a ‘pkg_add -u’ as root.  Based on the output, it is going through the
>> packages, checking for newer versions, and updating if there is one.
>> It then prints a “pkgname-oldver->newver” string.  The thing is, a lot
>> of the time the old version and new version is the same.  What does
>> this mean?  A slight tweak to a makefile or something that wasn’t
>> significant enough to rev the version number?  Some date discrepancy
>> with the mirror i am pulling it from?  I know it’s a small thing, but
>> it really has me puzzled.
> 
> It typically means that one of the libraries that the package depends on
> has been updated. This can be either a system library (included in the
> base system) or a third-party library (installed as a package). Because
> its dependencies are updated, the binary has to be relinked.
> 
> For what it's worth, this is also why you will see warnings like the one
> below if you run a binary that is out-of-sync with your libraries:
> 
>> WARNING: symbol(foo) size mismatch, relink your program


Thanks!  That makes sense.

Jordon

Re: Question about updating packages

[Michael McConville]

Jordon wrote:
> I have current running on some machines and multiple times a week I
> will update them by booting bsd.rd and doing the (u) option (i think
> that is the ‘proper’ way to update to the latest current base system).
> 
> I will occasionally update all the packages I have installed by doing
> a ‘pkg_add -u’ as root.  Based on the output, it is going through the
> packages, checking for newer versions, and updating if there is one.
> It then prints a “pkgname-oldver->newver” string.  The thing is, a lot
> of the time the old version and new version is the same.  What does
> this mean?  A slight tweak to a makefile or something that wasn’t
> significant enough to rev the version number?  Some date discrepancy
> with the mirror i am pulling it from?  I know it’s a small thing, but
> it really has me puzzled.

It typically means that one of the libraries that the package depends on
has been updated. This can be either a system library (included in the
base system) or a third-party library (installed as a package). Because
its dependencies are updated, the binary has to be relinked.

For what it's worth, this is also why you will see warnings like the one
below if you run a binary that is out-of-sync with your libraries:

> WARNING: symbol(foo) size mismatch, relink your program

Question about updating packages

[Jordon]

I have current running on some machines and multiple times a week I will update 
them by booting bsd.rd and doing the (u) option (i think that is the ‘proper’ 
way to update to the latest current base system).

I will occasionally update all the packages I have installed by doing a 
‘pkg_add -u’ as root.  Based on the output, it is going through the packages, 
checking for newer versions, and updating if there is one.  It then prints a 
“pkgname-oldver->newver” string.  The thing is, a lot of the time the old 
version and new version is the same.  What does this mean?  A slight tweak to a 
makefile or something that wasn’t significant enough to rev the version number? 
 Some date discrepancy with the mirror i am pulling it from?  I know it’s a 
small thing, but it really has me puzzled.

Jordon