From: | Zac Medico <zmedico@g.o> | ||
---|---|---|---|
To: | gentoo-portage-dev@l.g.o, Samuel Bernardo <samuelbernardo.mail@×××××.com> | ||
Subject: | [gentoo-portage-dev] Re: EAPI 6 | ||
Date: | Sat, 14 Mar 2020 21:30:33 | ||
Message-Id: | fe6fa169-9d28-c9fb-a4a8-9fbebd43773b@gentoo.org | ||
In Reply to: | [gentoo-portage-dev] Re: EAPI 6 by Samuel Bernardo |
1 | On 3/14/20 1:40 PM, Samuel Bernardo wrote: |
2 | > Thank you very much Zac for your answers. |
3 | > |
4 | > I was wondering if I was missing any coding convention after reading |
5 | > [1], since I always follow the pattern to define eclasses inside my |
6 | > overlays as needed, sometimes overriding those provided from gentoo |
7 | > portage. I was not sure if I was doing the development breaking the |
8 | > expected QA rules. |
9 | > |
10 | > With your explanation I know now that I'm doing it the right way. |
11 | > |
12 | > [1] |
13 | > https://devmanual.gentoo.org/appendices/common-problems/index.html#qa-notice----eclass-foo-inherited-illegally |
14 | |
15 | The stale cache issues that are mentioned there only applied to the |
16 | 'pms' cache format which should not be used since around 2012/2013 when |
17 | we changed the default for the metadata/layout.conf cache-formats |
18 | setting here: |
19 | |
20 | https://gitweb.gentoo.org/proj/portage.git/commit/?id=e760c8d2a4ccc56e351ac37904c715f596b58e42 |
21 | -- |
22 | Thanks, |
23 | Zac |
File name | MIME type |
---|---|
signature.asc | application/pgp-signature |