From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ]
Date: Fri, 9 Feb 2024 10:54:45 -0500 [thread overview]
Message-ID: <ZcZKxfPt1FFLNuvy@eversor> (raw)
In-Reply-To: <bb44addf-fc52-3d49-edbd-d7a629e72aa@woodpecker.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Fri, Feb 09, 2024 at 03:23:10PM +0000, Andrey Grozin wrote:
> Hello *,
>
> pkgcheck complains about each new version of dev-lisp/sbcl:
>
> UseFlagWithoutDeps: version 2.4.1: special small-files USE flag without
> effect on dependencies: [ unicode ]
>
> The USE flag "unicode" in the sbcl ebuild has nothing to do with
> installing / not installing any files, small or otherwise. It determins
> whether the produced lisp will support unicode internally:
>
> sbcl_feature "$(usep unicode)" ":sb-unicode"
>
> Usually this is desirable, so, in USE we have +unicode. Is there a way to
> silence these warnings?
Is there even any reason to ever disable unicode support? Point is that
why have USE for it? Or does it introduce additional dependencies?
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-09 15:54 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 [this message]
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
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=ZcZKxfPt1FFLNuvy@eversor \
--to=ionen@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