From: Ulrich Mueller <ulm@gentoo.org>
To: Sam James <sam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2 3/3] gnuconfig.eclass: use BDEPEND, BROOT where available (drop support for EAPI <4)
Date: Wed, 07 Apr 2021 13:06:12 +0200 [thread overview]
Message-ID: <ueefm73rv@gentoo.org> (raw)
In-Reply-To: <6645620A-C5FC-4026-B80D-D4C71FDA43A5@gentoo.org> (Sam James's message of "Tue, 6 Apr 2021 20:32:04 +0100")
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
>>>>> On Tue, 06 Apr 2021, Sam James wrote:
> 1) @system varies between profiles anyway which makes it hard to fully
> rely on;
That's exactly the reason why you _don't_* add GNU grep as a dependency,
because e.g. on Prefix grep may be provided by another package.
grep is a POSIX tool and a bootstrap package, so we can be certain that
will be available everywhere. (And the single grep instance in the
eclass doesn't use any GNUisms.)
> 2) As a few of us have discussed in #gentoo-portage in the past,
> continuing this trend of not explicitly stating dependencies makes
> parallelism in Portage difficult. You can try this with
> —implicit-system-deps=n, but we really need to be stating what we use
> explicitly.
This would mean that we'd end up with lots of system dependencies in
every ebuild. The current policy is in place for good reasons.
You may have a point for adding library dependencies explicitly, but
certainly not for common build tools (aka bootstrap packages). They will
be available from the very beginning of the bootstrap process.
> The benefit is enhanced parallelism and the downside is being
> _slightly_ more verbose in some ebuilds;
s/slightly/much/;s/some/all/
We'd end up having a significant subset of profiles/base/packages in
_every_ ebuild. Or even worse, a bunch of any-of-many dependencies or
virtuals, in order to account for different systems. Personally, I
wouldn't be willing to maintain such dependencies for my ebuilds.
More importantly, if you want such a policy change, then you should
discuss it first and have it approved. Until then, the current policy
[1] applies.
> 3) Implicit dependencies make it hard for us to ever actually swap
> implementations;
> 4) This helps when creating minimal systems without Portage in it.
[1] https://devmanual.gentoo.org/general-concepts/dependencies/index.html#implicit-system-dependency
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2021-04-07 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 14:06 [gentoo-dev] [PATCH v2 1/3] autotools.eclass: eclassdoc, cosmetic changes, drop old EAPIs, configure.ac rename Sam James
2021-04-05 14:06 ` [gentoo-dev] [PATCH v2 2/3] gnuconfig.eclass: provide basic @ECLASS block, docs Sam James
2021-04-05 14:06 ` [gentoo-dev] [PATCH v2 3/3] gnuconfig.eclass: use BDEPEND, BROOT where available (drop support for EAPI <4) Sam James
2021-04-05 16:24 ` Ulrich Mueller
2021-04-06 19:32 ` Sam James
2021-04-07 11:06 ` Ulrich Mueller [this message]
2021-04-09 23:30 ` Sam James
2021-04-07 11:18 ` Michael Orlitzky
2021-04-07 11:30 ` Ulrich Mueller
2021-04-09 23:32 ` Sam James
2021-04-10 0:13 ` Michael Orlitzky
2021-04-10 0:19 ` Sam James
2021-04-10 3:54 ` Alec Warner
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=ueefm73rv@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=sam@gentoo.org \
/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