From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ]
Date: Sun, 11 Feb 2024 03:46:57 +0000 [thread overview]
Message-ID: <8734tzsluq.fsf@gentoo.org> (raw)
In-Reply-To: <bff3bd60-5658-4750-8a1f-5dd260fb5f16@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
Eli Schwartz <eschwartz93@gmail.com> writes:
> [[PGP Signed Part:Undecided]]
> On 2/9/24 7:04 PM, Sam James wrote:
>>
>> Eli Schwartz <eschwartz93@gmail.com> writes:
>>> Often, USE flags have an obvious point even without selecting or
>>> deselecting dependencies -- usually because their maintainers took care
>>> in describing it in metadata.xml.
>>>
>>
>> To pick up on this point: yes, if one concludes the USE flag has merit
>> and the global description is either poor or has some reason to be
>> considered spurious in the case of the package, you should consider
>> documenting it to avoid this question.
>>
>> Adding a suppression like https://github.com/pkgcore/pkgcheck/issues/478
>> proposes should really be accompanied by such an improvement anyway for
>> the benefit of users.
>
>
> I'd like to request in the event that this pkgcheck ticket is
> implemented, that including a description in metadata.xml which provides
> additional package specific information (or, programmatically, "is
> non-empty and un-equal to the global description") is made mandatory for
> the purposes of silencing this warning... :)
parona ended up messaging me and pointing out that
https://pkgcore.github.io/pkgcheck/man/pkgcheck.html#useflagwithoutdeps
already says...
> In cases where this USE flag is appropriate, you can silence this
> warning by adding a description to this USE flag in metadata.xml file
> and thus making it a local USE flag instead of global one.
which I think pretty much solves the full thing already...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2024-02-11 3:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 15:23 [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ] Andrey Grozin
2024-02-09 15:43 ` Mike Gilbert
2024-02-09 15:54 ` Ionen Wolkens
2024-02-09 16:07 ` Michael Orlitzky
2024-02-09 16:57 ` Mike Gilbert
2024-02-09 17:17 ` Michael Orlitzky
2024-02-09 18:40 ` Mike Gilbert
2024-02-09 19:09 ` Eli Schwartz
2024-02-09 19:57 ` Michael Orlitzky
2024-02-09 21:04 ` Eli Schwartz
2024-02-09 21:25 ` Michael Orlitzky
2024-02-09 21:56 ` Eli Schwartz
2024-02-09 22:56 ` stefan11111
2024-02-10 0:03 ` Matt Jolly
2024-02-10 11:48 ` David Seifert
2024-02-10 17:26 ` stefan11111
2024-02-11 0:58 ` Eli Schwartz
2024-02-10 11:22 ` orbea
2024-02-11 0:58 ` Eli Schwartz
2024-02-10 0:04 ` Sam James
2024-02-11 0:42 ` Eli Schwartz
2024-02-11 3:46 ` Sam James [this message]
2024-02-11 3:56 ` Eli Schwartz
2024-02-12 4:54 ` Andrey Grozin
2024-02-10 0:00 ` Sam James
2024-02-09 23:52 ` Sam James
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=8734tzsluq.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev@lists.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