* [gentoo-portage-dev] Re: [PATCH] emerge(1): document --oneshot caveats (bug 563482)
@ 2015-10-21 1:51 99% ` Duncan
0 siblings, 0 replies; 1+ results
From: Duncan @ 2015-10-21 1:51 UTC (permalink / raw
To: gentoo-portage-dev
Rob Wortman posted on Tue, 20 Oct 2015 17:37:37 -0700 as excerpted:
> On 2015-10-20 at 21:44:58 +0200, bernalex@gentoo.org wrote:
>> (since it's describing somewhat complicated functionality)
>
> So, I'm curious what's actually going on there. If I emerge packages
> with --oneshot, does that create the possibility of broken dependencies
> for world-reachable packages, or does updating @world create the
> possiblity of broken dependencies for oneshot'ed packages?
AFAIK, the latter. @world's dep-calc doesn't take into account anything
beyond what's in @world (which by definition includes @system and, where
appropriate, @profile). So @world should be safe, but packages not in it
or deps of what's in it aren't accounted for and both won't be updated,
and could be unmerged if the depgraph that portage calculates for @world
works most directly by doing so.
They won't be unmerged unless they're simple-blockers to something,
however; that's what depclean is for. It's just that portage doesn't
account for them in the depgraph, either, and thus might "accidentally"
unmerge them.
Meanwhile, the suggestion that --update --deep avoids the problem is most
interesting to me, since all my normally used update-everything scripts
have included --deep for nigh on a decade, now, while my normally used
named-merge scripts have included --oneshot, since back in the day I
didn't want to inadvertently pollute my world file with manually merged
deps, and these days I don't even have an @world file, only a world_sets
file, which names the various sets I've grouped the contents of both my
former @world file and my former @system set (which is nullified, no
@system packages at all, here, with everything I decided I actually
needed in @world).
Plus, I reasonably commonly use merged but not assigned to a set packages
as a sort of temporary package purgatory, for testing until I've decided
I either like the package enough to keep, in which case I add it to the
appropriate set as named in @world_sets, or I don't, in which case I
simply run depclean and it cleans up both the package and any deps that
only it pulled in, without cleaning up anything else, since I always run
depclean in --ask mode after an update, simply to keep my system free of
any detritus.
But I'm not sure of the avoidance mechanism, since for all I knew,
without @world pinning them in, portage's depgraph didn't include them
and that was that, --deep or not.
So the connection between --deep and --oneshot is new to me, and I'd love
to know more about the implications.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2015-10-20 19:29 [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482) Zac Medico
2015-10-20 19:44 ` Alexander Berntsen
2015-10-21 0:37 ` Rob Wortman
2015-10-21 1:51 99% ` [gentoo-portage-dev] " Duncan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox