Is it better to us emerge -U or emerge -N
I've always done -N but it didn't go very smoothly it seems to me -U might be better option but it takes longer.
Right now I'm doing -U and it is compiling 549-packages.
Is it better to us emerge -U or emerge -N
I've always done -N but it didn't go very smoothly it seems to me -U
might be better option but it takes longer.
Right now I'm doing -U and it is compiling 549-packages.
Am 10.04.23 um 18:44 schrieb thelma@sys-concept.com:
Is it better to us emerge -U or emerge -N
I've always done -N but it didn't go very smoothly it seems to me -U might be better option but it takes longer.
Right now I'm doing -U and it is compiling 549-packages.
Just out of curiosity: Is that your update process for world or in which context do you use it? If this is your update process, with which other options do you combine it? 549-packages is quit a lot.
Is it better to us emerge -U or emerge -N
I've always done -N but it didn't go very smoothly it seems to me -U
might be better option but it takes longer.
Right now I'm doing -U and it is compiling 549-packages.
.
thelma@sys-concept.com wrote:
Is it better to us emerge -U or emerge -N
I always do both except I use the lower case 'u'. I started using
Gentoo back in 2003. Over the years, I added/changed options to emerge until I got a good sane system that works as expected and is stable. My command is emerge -auDN world and it has worked for years.
On 2023-04-11, Dale <rdalek1967@gmail.com> wrote:
thelma@sys-concept.com wrote:Once upon a time, a little over 20 years ago, I did some studying, and
Is it better to us emerge -U or emerge -NI always do both except I use the lower case 'u'. I started using
Gentoo back in 2003. Over the years, I added/changed options to emerge
until I got a good sane system that works as expected and is stable. My
command is emerge -auDN world and it has worked for years.
I searched mailing lists postings for recommendations, and I settled
on
emerge -auvND
I've been using that ever since on a handful of machines. I'd have to
spend a few minutes reading the man page to remember the significance
of a couple of the flags, but I note that differs only in verbosity
from Dale's usage.
--
Grant
On 4/10/23 18:53, Dale wrote:
I've asked ChatGPT for explanation and here is what I got:
Here are the differences between emerge -U and emerge -N:
emerge -U: This option upgrades the specified package(s) to the
latest available version. It will first download the new version,
then build and install it. If a dependency of the package being
upgraded also needs to be upgraded, it will also be upgraded.
emerge -N: This option installs the specified package(s) without
upgrading any dependencies. It will only download and install the
package(s) if they are not already installed. If any dependencies of
the package(s) are not already installed, the command will fail.
In other words, emerge -U upgrades packages and their dependencies,
while emerge -N only installs packages without upgrading any
dependencies.
thelma@sys-concept.com wrote:
Is it better to us emerge -U or emerge -N
I've always done -N but it didn't go very smoothly it seems to me -U
might be better option but it takes longer.
Right now I'm doing -U and it is compiling 549-packages.
.
I always do both except I use the lower case 'u'. I started using
Gentoo back in 2003. Over the years, I added/changed options to emerge until I got a good sane system that works as expected and is stable. My command is emerge -auDN world and it has worked for years. One
difference, I update once a week and on occasion two weeks if I have something going on and need to wait. I'd think tho, if one goes a long
time between updates, my way would result in a longer compile time but
also a system that is more stable or clean.
Everyone has their own way. If what a person does is working, by all
means do it that way. I picked my way because of problems I ran into.
The solutions to those problems resulted in the command I use. If one
waits a long time between updates, more packages will have updated and
result in more updates regardless of the options. In that case, any USE changes would apply to those packages anyway. If one updates often, as
I do, then the way I do it may have benefits and result in a more stable system, even tho it requires more packages to compile.
Hope that helps.
Dale
:-) :-)
!'ve asked ChatGPT for explanation and here is what I got:
Here are the differences between emerge -U and emerge -N:
emerge -U: This option upgrades the specified package(s) to the latest available version. It will first download the new version, then build
and install it. If a dependency of the package being upgraded also
needs to be upgraded, it will also be upgraded.
emerge -N: This option installs the specified package(s) without
upgrading any dependencies. It will only download and install the
package(s) if they are not already installed. If any dependencies of
the package(s) are not already installed, the command will fail.
I always do both except I use the lower case 'u'. I started using
Gentoo back in 2003. Over the years, I added/changed options to
emerge until I got a good sane system that works as expected and is
stable. My command is emerge -auDN world and it has worked for years.
Once upon a time, a little over 20 years ago, I did some studying, and
I searched mailing lists postings for recommendations, and I settled
on
emerge -auvND
On Mon, 2023-04-10 at 22:10 -0600, thelma@sys-concept.com wrote:
On 4/10/23 18:53, Dale wrote:This is a good example of why ChatGPT cannot be trusted.
I've asked ChatGPT for explanation and here is what I got:
Here are the differences between emerge -U and emerge -N:
emerge -U: This option upgrades the specified package(s) to the
latest available version. It will first download the new version,
then build and install it. If a dependency of the package being
upgraded also needs to be upgraded, it will also be upgraded.
emerge -N: This option installs the specified package(s) without
upgrading any dependencies. It will only download and install the
package(s) if they are not already installed. If any dependencies of
the package(s) are not already installed, the command will fail.
In other words, emerge -U upgrades packages and their dependencies,
while emerge -N only installs packages without upgrading any
dependencies.
When ChatGPT doesn't know the answer to something, rather than saying
it doesn't know the answer, it just makes it up.
The difference between -U and -N as explained by ChatGPT is wrong; in
fact, it has nothing to do with dependencies.
To have a truthful answer, let's not ask ChatGPT and instead look at
`man 5 emerge`:
--newuse, -N
Tells emerge to include installed packages where USE
flags have changed since compilation. This option also
implies the --selective option. USE flag changes
include:
A USE flag was added to a package. A USE flag was
removed from a package. A USE flag was
turned on for
a package. A USE flag was turned off for a package.
--changed-use, -U
Tells emerge to include installed packages where USE
flags have changed since installation. This option
also implies the --selective option. Unlike --newuse,
the --changed-use option does not trigger
reinstallation when flags that the user has not
enabled are added orremoved.
In a nutshell, `--newuse` or `-N` rebuilds packages when USE flags have changed, regardless of whether the changed USE flags affect the outcome
Where as `--changed-use` or `-U` rebuilds packages when the USE flags
have changed, AND the changed USE flags affect the outcome.
For example, suppose you are on an openRC system, and a package
introduces a new `systemd` USE flag;
With `-N`: this package will be rebuilt with `-systemd`
With `-U`: this package will not be rebuilt
On Tue, 11 Apr 2023 01:49:50 -0000 (UTC), Grant Edwards wrote:
I used that for a while, except like Dale I prefer to not use -v (I likeI always do both except I use the lower case 'u'. I started usingOnce upon a time, a little over 20 years ago, I did some studying, and
Gentoo back in 2003. Over the years, I added/changed options to
emerge until I got a good sane system that works as expected and is
stable. My command is emerge -auDN world and it has worked for years.
I searched mailing lists postings for recommendations, and I settled
on
emerge -auvND
the quiet life) but I switched to -U (--changed-use) to lower the number
of unnecessary rebuilds.
The info from the man page is correct.
They do two different things. The -N will mean more recompiles of packages but it also means that when a USE flag change is made, it also changes any packages that relates to that. In other words, it goes deeper.
...
So now we kn ow, ChatGPT is case-insensitive, it gave you answers for -u
and -n.
On Tuesday, 11 April 2023 11:33:38 BST Dale wrote:
The info from the man page is correct.Of course it is. There'd be uproar if it weren't.
They do two different things. The -N will mean more recompiles of packages >> but it also means that when a USE flag change is made, it also changes any >> packages that relates to that. In other words, it goes deeper.I don't know why you think it goes deeper, Dale. It's a question of candidate selection, not depth of analysis.
-U: if a package doesn't need to be updated on your system today, it'll be left until it does.
-N: if any USE flag at all has changed in a package, it'll be recompiled, whether it needs to be on your system or not.
-U: if a package doesn't need to be updated on your system today,
it'll be left until it does.
-N: if any USE flag at all has changed in a package, it'll be
recompiled, whether it needs to be on your system or not.
When I say deeper, I mean it will find more packages that may not be
found otherwise.
On Tue, 11 Apr 2023 06:30:47 -0500, Dale wrote:
And -e finds even more - but more is not always better. -U was introduced because -N was causing too many packages to be rebuilt unnecessarily.-U: if a package doesn't need to be updated on your system today,
it'll be left until it does.
-N: if any USE flag at all has changed in a package, it'll be
recompiled, whether it needs to be on your system or not.
When I say deeper, I mean it will find more packages that may not be
found otherwise.
When I say deeper, I mean it will find more packages that may not beAnd -e finds even more - but more is not always better. -U was
found otherwise.
introduced because -N was causing too many packages to be rebuilt unnecessarily.
Before those options came along, I would run emerge -e world to fix problems. Sometimes revdep-rebuild would catch things but sometimes it wouldn't. Thing is, since I started using the current options, I have
few problems with package upgrades. Sure, they have a known bug on
occasion but recompiling won't help that. I'm just talking about
problems with one package not matching up with some other package and recompile fixes it.
To me, the fact it works so much better tells me I'm doing something
right. Other people may get different results but as long as what I'm
doing works, I don't plan to change anything.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 302 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 96:59:39 |
| Calls: | 6,764 |
| Calls today: | 2 |
| Files: | 12,295 |
| Messages: | 5,376,370 |
| Posted today: | 1 |