Re: [gentoo-dev] New customization options available on packages.g.o
On 10/6/20 11:55 PM, Max Magorsch wrote: > For example, it's possible to customize the keywords that are shown or > the classes of pkgcheck warnings that are displayed. Furthermore it's > also possible to include all packages, QA reports, pull requests and > bugs of projects a maintainer is part of on the maintainer page. This > way, it's for instance possible to view all bugs of packages you are > maintaining as well as bugs of packages that are maintained by > projects you are part of. > > Further customization options are available on the preferences pages. > Feel free to let me know if you are missing anything. Apart from that: > Happy customizing. > > /M > A link to everyone: https://packages.gentoo.org/user/preferences/packages Is this cookie-based? Is there a way to "save" your preferences somehow, or would you need to introduce a new login account to p.g.o? How's the "single-login-to-all-gentoo-services" idea moving? Still this is awesome and thanks for your work on p.g.o. I'm off to test some settings. -- juippis OpenPGP_signature Description: OpenPGP digital signature
[gentoo-dev] Re: EAPI conditional in eclasses (was: [PATCH v2 1/6] verify-sig.eclass: New eclass to verify OpenPGP sigs)
> On Tue, 06 Oct 2020, William Hubbs wrote:
>> +case "${EAPI:-0}" in
>> +0|1|2|3|4|5|6)
>> +die "Unsupported EAPI=${EAPI} (obsolete) for ${ECLASS}"
>> +;;
>> +7)
>> +;;
>> +*)
>> +die "Unsupported EAPI=${EAPI} (unknown) for ${ECLASS}"
>> +;;
>> +esac
> Does it really matter that an EAPI is unsupported because it is
> obsolete vs unknown? Can we simplify this case statement to the
> following or something similar for all of our eclasses?
> case "${EAPI:-0}" in
> 7)
> ;;
> *)
> die "Unsupported EAPI=${EAPI} (unknown) for ${ECLASS}"
> ;;
> esac
I am with you there, at least for a new eclass that never supported
these old EAPIs.
It may be somewhat useful when removing existing support for an EAPI,
but even there things should be clear from context?
Ulrich
signature.asc
Description: PGP signature
Re: [gentoo-dev] [PATCH v2 4/6] app-crypt/openpgp-keys-miniupnp: Package keys used by miniupnp upst
On Tue, Oct 06, 2020 at 06:17:23PM +, Robin H. Johnson wrote: > I'm worried about the proliferation of tiny packages just to convey the > keys; and how versioning should work if upstream rotates their keys. That was my initial reaction as well. The app-crypt/openpgp-keys-* will potentially double the number of packages in the tree. We can probably come up with a better design. I agree with the need to make it easier for developers to check sigs before signing the manifest btw. Thanks for that -- Eray
