From: "Michał Górny" <mgorny@gentoo.org>
To: Rich Freeman <rich0@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review
Date: Sat, 17 Oct 2015 14:51:40 +0200 [thread overview]
Message-ID: <20151017145140.7594c244.mgorny@gentoo.org> (raw)
In-Reply-To: <CAGfcS_kYnHjY+X-cg+WcH3UZpds0-eYs+36DTb7iXJFKo92udg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Dnia 2015-10-17, o godz. 08:38:51
Rich Freeman <rich0@gentoo.org> napisał(a):
> On Sat, Oct 17, 2015 at 8:25 AM, hasufell <hasufell@gentoo.org> wrote:
> > On 10/17/2015 02:19 PM, Jason A. Donenfeld wrote:
> >>
> >> The other question is more critical -- could you merge eapply and
> >> eapply_user? Or add some hook to PMS so that eapply_user isn't needed?
> >> IOW, it'd be nice if every package was, by default, patchable by the user.
> >>
> >
> > IMO, eapply_user should not be in the eclass and not in PMS. patches are
> > something that can easily be done via PM hooks, if the PM has proper
> > hooks support.
> >
>
> The reason this was done was to give maintainers more control over
> WHEN patches are applied, while still ensuring they are applyied.
>
> The other feature that is supposed to be in EAPI6 (I didn't read the
> draft yet) is that the PM should refuse to install the package if
> eapply is never called (ie src_prepare is overridden and the ebuild
> didn't call eapply). It is required that all ebuilds call it once
> unconditionally. That way users don't get inconsistent behavior from
> package to package and be dependent on maintainers to fix it.
>
> We'd have to dig through the archives, but I'm sure there was
> extensive discussion about whether this belonged in the PM or PMS.
I don't think this was really accepted. I think the best we can do is
make repoman complain about it.
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2015-10-17 12:52 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22049.17676.1822.986579@a1i15.kph.uni-mainz.de>
2015-10-17 12:19 ` [gentoo-dev] Re: [gentoo-dev-announce] EAPI 6 draft for review Jason A. Donenfeld
2015-10-17 12:21 ` Jason A. Donenfeld
2015-10-17 12:24 ` Michał Górny
2015-10-17 12:28 ` hasufell
2015-10-17 12:52 ` Ulrich Mueller
2015-10-17 12:56 ` hasufell
2015-10-17 13:07 ` Ulrich Mueller
2015-10-17 15:22 ` hasufell
2015-10-17 16:40 ` Alexis Ballier
2015-10-17 22:16 ` Rich Freeman
2015-10-18 8:33 ` Alexis Ballier
2015-10-18 9:54 ` Ulrich Mueller
2015-10-18 9:56 ` Alexis Ballier
2015-10-18 10:13 ` Michał Górny
2015-10-18 10:17 ` Ulrich Mueller
2015-10-18 10:49 ` Rich Freeman
2015-10-19 7:12 ` Alexis Ballier
2015-10-19 7:22 ` Anthony G. Basile
2015-10-19 7:28 ` Alexis Ballier
2015-10-19 8:25 ` Ulrich Mueller
2015-10-19 8:31 ` Alexis Ballier
2015-10-19 7:58 ` Michał Górny
2015-10-19 8:04 ` Alexis Ballier
2015-10-19 8:09 ` Michał Górny
2015-10-19 8:17 ` Alexis Ballier
2015-10-19 8:07 ` Anthony G. Basile
2015-10-19 22:07 ` Andreas K. Huettel
2015-10-19 12:38 ` Rich Freeman
2015-10-19 13:34 ` Alexis Ballier
2015-10-19 13:51 ` Rich Freeman
2015-10-19 14:21 ` Alexis Ballier
2015-10-19 17:17 ` Rich Freeman
2015-10-19 18:28 ` Alexis Ballier
2015-10-19 19:49 ` Rich Freeman
2015-10-20 7:51 ` Alexis Ballier
2015-10-20 8:57 ` Rich Freeman
2015-10-20 9:22 ` Alexis Ballier
2015-10-20 10:00 ` Rich Freeman
2015-10-20 10:25 ` Alexis Ballier
2015-10-21 1:24 ` Duncan
2015-10-21 7:29 ` Alexis Ballier
2015-10-18 10:36 ` Alexis Ballier
2015-10-20 7:47 ` Daniel Campbell
2015-10-20 8:00 ` Alexis Ballier
2015-10-17 12:42 ` Ulrich Mueller
2015-10-17 12:25 ` hasufell
2015-10-17 12:38 ` Rich Freeman
2015-10-17 12:49 ` hasufell
2015-10-17 12:56 ` Rich Freeman
2015-10-17 13:02 ` hasufell
2015-10-17 13:47 ` Alexis Ballier
2015-10-17 15:00 ` hasufell
2015-10-17 16:07 ` Anthony G. Basile
2015-10-17 16:35 ` Alexis Ballier
2015-10-17 18:03 ` Ciaran McCreesh
2015-10-18 11:37 ` hasufell
2015-10-18 11:43 ` Rich Freeman
2015-10-18 12:05 ` hasufell
2015-10-18 12:24 ` Rich Freeman
2015-10-17 12:51 ` Michał Górny [this message]
2015-10-17 19:15 ` Rich Freeman
2015-10-17 20:08 ` Alexis Ballier
2015-10-17 20:47 ` Ulrich Mueller
2015-10-18 8:31 ` Alexis Ballier
2015-10-18 8:48 ` Michał Górny
2015-10-18 9:23 ` Alexis Ballier
2015-10-18 10:07 ` Michał Górny
2015-10-18 10:34 ` Alexis Ballier
2015-10-18 11:54 ` Andreas K. Huettel
2015-10-18 11:57 ` Alexis Ballier
2015-10-18 12:44 ` Ciaran McCreesh
2015-10-18 13:01 ` Rich Freeman
2015-10-18 18:00 ` Alexis Ballier
2015-10-18 18:06 ` Ciaran McCreesh
2015-10-18 18:19 ` Alexis Ballier
2015-10-18 18:36 ` Ciaran McCreesh
2015-10-18 19:20 ` Alexis Ballier
2015-10-17 21:24 ` Michał Górny
2015-10-18 8:47 ` Alexis Ballier
2015-10-18 9:01 ` Michał Górny
2015-10-18 9:34 ` Alexis Ballier
2015-10-18 10:09 ` Michał Górny
2015-10-18 10:31 ` Alexis Ballier
2015-10-20 18:55 ` [gentoo-dev] utilizing BASH_COMPAT to smooth upgrades Mike Frysinger
2015-10-20 22:03 ` Ulrich Mueller
2015-10-20 22:51 ` Mike Frysinger
2015-10-21 7:34 ` [gentoo-dev] [PATCH] Recommend setting the bash compatibility level. (was: Re: utilizing BASH_COMPAT to smooth upgrades) Ulrich Mueller
2015-10-22 13:55 ` [gentoo-dev] " Mike Frysinger
2015-10-22 15:00 ` Ulrich Mueller
2015-10-22 15:21 ` Mike Frysinger
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=20151017145140.7594c244.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=rich0@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