From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org, michael.lienhardt@laposte.net
Subject: Re: [gentoo-portage-dev] precisions on installed packages' dependencies
Date: Sun, 22 Mar 2020 18:01:07 -0700 [thread overview]
Message-ID: <2f3e382c-67d5-3bc5-e1c0-8df1c8b5f7ab@gentoo.org> (raw)
In-Reply-To: <1914109345.7077150.1584923899601.JavaMail.zimbra@laposte.net>
[-- Attachment #1.1: Type: text/plain, Size: 1405 bytes --]
On 3/22/20 5:38 PM, michael.lienhardt@laposte.net wrote:
> Dear all,
>
> Still in the process of improving my solver (and make it a usable tool), I need to have a better idea on how installed packages should be managed.
Great!
> I didn't find anything on that topic in the PMS (if I've missed it, I'm sorry).
> Could you confirm/correct my following understanding:
> 1. installed packages that are still in the portage tree can be unmerged/updated without any restriction (as specified in their .ebuild)
True.
> 2. installed packages that are not in the portage tree can only be kept as is or unmerged
Installed packages may also implement pkg_config and pkg_info phases
that can be executed via emerge --config and emerge --info.
> 3. before removing a library, "ebuild unmerge" always checks if it is used by another package: this means that installed packages' dependencies are never broken.
That's true if the package is removed via emerge --depclean, but emerge
--unmerge does not account for dependencies.
Also, it's possible for dependencies of installed packages to be
temporarily broken by upgrades. In cases like this, the breakage will
eventually be resolved by a rebuild (which occurs automatically for slot
operator := deps), upgraded, or by emerge --depclean (which removes
unneeded packages).
>
> Many thanks!
> Michael
>
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2020-03-23 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 0:38 [gentoo-portage-dev] precisions on installed packages' dependencies michael.lienhardt
2020-03-23 1:01 ` Zac Medico [this message]
2020-03-23 22:21 ` Re : " michael.lienhardt
2020-03-24 4:13 ` Zac Medico
2020-03-24 18:31 ` michael.lienhardt
2020-03-26 8:06 ` Alec Warner
2020-03-27 13:59 ` michael.lienhardt
2020-03-28 6:48 ` Alec Warner
2020-03-30 21:55 ` michael.lienhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f3e382c-67d5-3bc5-e1c0-8df1c8b5f7ab@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=michael.lienhardt@laposte.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox