On Tue, 2022-02-22 at 12:57 -0500, Michael Orlitzky wrote:
>
> But --changed-use slows things down a lot, so you also don't want to
> use it *every* time.
>
Whoops, I mean --changed-deps.
On Tue, 2022-02-22 at 16:42 +0100, Dr Rainer Woitok wrote:
>
> So for people like me, neither being a developer nor managing a local
> server for binary packages (thanks Andreas for pointing out this special
> case), "--changed-deps" really is an option not to be used.
>
> Case finally closed
Thanks, Michael,
On Tuesday, 2022-02-22 10:05:06 -0500, you wrote:
> ...
> It's really a (portage-only) workaround for developers who don't follow
> the rules, thus ensuring that we'll never have another competing
> package manager again.
So for people like me, neither being a developer nor m
On Tue, 2022-02-22 at 14:26 +, Neil Bothwick wrote:
>
> It's not a relic, it's a fairly recent addition. It's a bit of a belt and
> braces approach which basically says "rebuild everything that might just
> possibly, maybe, in some circumstances have some sort of effect".
>
>
It's really a
On Tue, 22 Feb 2022 13:21:48 +0100, Dr Rainer Woitok wrote:
> Apart from a reply by Dale which more or less confirmed (at least the
> way I read it) that the section regarding the "--changed-deps" option in
> "man emerge" does not contain much valuable information, there was no
> response wh
On Tue, 22 Feb 2022 14:09:30 +0100, Ramon Fischer wrote:
> Is it a good practise to update @system first?
>
> I always update @world almost every seven days and I only get into
> package conflicts, if I do not update for more than 60 days or so. Last
> time was 99 days ago and I had to resolve
On Tue, 22 Feb 2022 13:21:48 +0100
Dr Rainer Woitok wrote:
> And none of the examples to overcome problems provided by others in this
> thread ever contained "--changed-deps". Does this mean "--changed-deps"
> is a NOOP, a relict from days long gone by, meanwhile without any funct-
> ionality,
Is it a good practise to update @system first?
I always update @world almost every seven days and I only get into
package conflicts, if I do not update for more than 60 days or so. Last
time was 99 days ago and I had to resolve circular package dependencies
and so forth manually.
I wrote thi
Er ...
On Monday, 2022-02-21 11:13:16 +0100, I myself wrote:
> ...
> But what
> about "--changed-deps"? Can nobody on this list explain what it really
> is or isn't good for, or when to use or not to use it?
Apart from a repl
Am 22.02.2022 um 06:27 schrieb Andreas Fink:
On Mon, 21 Feb 2022 22:26:30 +0100
hitachi303 wrote:
emerge -av --depclean
emerge -a --depclean --with-bdeps=n
only then when there are as few programs installed as possible I run
emerge --sync
emerge -Dua --reinstall changed-use @world
I t
Am 21.02.2022 um 22:48 schrieb Neil Bothwick:
On Mon, 21 Feb 2022 22:26:30 +0100, hitachi303 wrote:
When running an update after a long long time my approach is as follows:
emerge -av --depclean
You don't need to unmerge them, just add --exclude "firefox thunderbird
etc" to your emerge comm
On Mon, 21 Feb 2022 22:26:30 +0100
hitachi303 wrote:
>
> emerge -av --depclean Stuff like firefox, thunderbird, etc.>
>
> emerge -a --depclean --with-bdeps=n
>
> only then when there are as few programs installed as possible I run
> emerge --sync
>
> emerge -Dua --reinstall changed-use @world
I
On Mon, 21 Feb 2022 22:26:30 +0100, hitachi303 wrote:
> When running an update after a long long time my approach is as follows:
>
> emerge -av --depclean Stuff like firefox, thunderbird, etc.>
You don't need to unmerge them, just add --exclude "firefox thunderbird
etc" to your emerge command.
Am 20.02.22 um 16:18 schrieb Wols Lists:
On 20/02/2022 14:54, Arve Barsnes wrote:
On Sun, 20 Feb 2022 at 15:40, Dr Rainer
Woitok wrote:
But if I understand the "emerge" manual page correctly, "--changed-deps"
causes a rebuild of a package, if one of its dependencies has been re-
build, eve
Neil Bothwick wrote:
> On Mon, 21 Feb 2022 05:38:09 -0600, Dale wrote:
>
>> P. S. I tried tkman to read man pages. It pukes a error and doesn't
>> work. Something changed in the man command and I don't like it. I'm
>> looking for a GUI man page tool. Any ideas? Off list if needed. I
>> notic
On Mon, 21 Feb 2022 05:38:09 -0600, Dale wrote:
> P. S. I tried tkman to read man pages. It pukes a error and doesn't
> work. Something changed in the man command and I don't like it. I'm
> looking for a GUI man page tool. Any ideas? Off list if needed. I
> noticed this when trying to read
Dr Rainer Woitok wrote:
> Wol,
>
> On Sunday, 2022-02-20 14:56:20 +, you wrote:
>
>> ...
>>But --deep - that's to do
>> with a dependency changing USE flags, and it will block a depclean if
>> you don't do it.
> Thanks for the reminder! This is
Wol,
On Sunday, 2022-02-20 14:56:20 +, you wrote:
> ...
>But --deep - that's to do
> with a dependency changing USE flags, and it will block a depclean if
> you don't do it.
Thanks for the reminder! This is in fact mentioned in every output
On Mon, 2022-02-21 at 00:12 +0200, j...@clusters.gr wrote:
> Pardon me, but how would using --nodeps be a wise choice to rebuild
> your @world?
Straightaway, it isn't. But if you've already computed the list of
packages to be emerged, and the order in which to emerge them, then
emerging those one
On 20/02/2022 22:05, Michael Orlitzky wrote:
You'd think, but --keep-going tries to recompute dependencies and if
the original emerge crashes in an inconsistent state, that often seems
to push the calculation over the edge, preventing portage from figuring
out how to proceed.
That's where I wou
Pardon me, but how would using --nodeps be a wise choice to rebuild your
@world?
> 21/2/22 v 0:06, Michael Orlitzky :
>
> On Sun, 2022-02-20 at 19:51 +, Neil Bothwick wrote:
>>
>> Shouldn't --keep-going have kicked in there and restarted the update?
>>
>
> You'd think, but --keep-going
On Sun, 2022-02-20 at 19:51 +, Neil Bothwick wrote:
>
> Shouldn't --keep-going have kicked in there and restarted the update?
>
You'd think, but --keep-going tries to recompute dependencies and if
the original emerge crashes in an inconsistent state, that often seems
to push the calculation
On 20/02/2022 19:51, Neil Bothwick wrote:
On Sun, 20 Feb 2022 11:49:45 -0500, Michael Orlitzky wrote:
So basically, dont-stop would update everything it can.
I half-jokingly called this "emerge --i-dont-care" in 2012:
https://groups.google.com/g/linux.gentoo.user/c/wE2GnF7RlnY
There are
On Sun, 20 Feb 2022 11:49:45 -0500, Michael Orlitzky wrote:
> > So basically, dont-stop would update everything it can.
>
> I half-jokingly called this "emerge --i-dont-care" in 2012:
>
> https://groups.google.com/g/linux.gentoo.user/c/wE2GnF7RlnY
>
> There are (still) a lot of people who w
On Sun, 2022-02-20 at 15:18 +, Wols Lists wrote:
>
> So basically, dont-stop would update everything it can.
I half-jokingly called this "emerge --i-dont-care" in 2012:
https://groups.google.com/g/linux.gentoo.user/c/wE2GnF7RlnY
There are (still) a lot of people who want it. Last night I
Wols Lists wrote:
> On 20/02/2022 14:54, Arve Barsnes wrote:
>> On Sun, 20 Feb 2022 at 15:40, Dr Rainer
>> Woitok wrote:
>>> But if I understand the "emerge" manual page correctly,
>>> "--changed-deps"
>>> causes a rebuild of a package, if one of its dependencies has been
>>> re-
>>> build, even
Dr Rainer Woitok wrote:
> Greetings,
>
> some time back it was pointed out on this list to only use "--changed-
> use" rather than "--newuse". So I've meanwhile removed this option (and
> also a few others) from my update script which I had created early after
> installing Gentoo. It now basical
On 20/02/2022 14:54, Arve Barsnes wrote:
On Sun, 20 Feb 2022 at 15:40, Dr Rainer Woitok wrote:
But if I understand the "emerge" manual page correctly, "--changed-deps"
causes a rebuild of a package, if one of its dependencies has been re-
build, even though the package does not require the ne
On 20/02/2022 14:40, Dr Rainer Woitok wrote:
Or does it just cause plenty of package rebuilds without
any real effect? Likewise, what about "--deep"? Should I keep it?
Changed deps, I don't particularly know about. But --deep - that's to do
with a dependency changing USE flags, and it will
On Sun, 20 Feb 2022 at 15:40, Dr Rainer Woitok wrote:
> But if I understand the "emerge" manual page correctly, "--changed-deps"
> causes a rebuild of a package, if one of its dependencies has been re-
> build, even though the package does not require the newer version of the
> dependency. So d
Greetings,
some time back it was pointed out on this list to only use "--changed-
use" rather than "--newuse". So I've meanwhile removed this option (and
also a few others) from my update script which I had created early after
installing Gentoo. It now basically runs
$ sudo emerge --ask --v
31 matches
Mail list logo
