From: Ulrich Mueller <ulm@gentoo.org>
To: Andrey Grozin <grozin@woodpecker.gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] are there any lisps in the default/linux/amd64/17.0/musl profile?
Date: Sun, 23 Jul 2023 11:26:56 +0200 [thread overview]
Message-ID: <uy1j7geqn@gentoo.org> (raw)
In-Reply-To: <67566f1b-4aa9-15e4-4e72-3def6ff26ce6@woodpecker.gentoo.org> (Andrey Grozin's message of "Sun, 23 Jul 2023 09:20:27 +0000 (UTC)")
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
>>>>> On Sun, 23 Jul 2023, Andrey Grozin wrote:
> It seems that there are no lisps in this profile. This may be correct.
> But where are all lisps masked? I see only
> grozin@bilbo /home/gentoo/profiles $ find -name package.mask | xargs
> fgrep lisp
> ./arch/powerpc/ppc64/package.mask:dev-lisp/sbcl
> ./arch/powerpc/ppc64/32ul/package.mask:-dev-lisp/sbcl
> ./arch/powerpc/ppc64/64le/package.mask:-dev-lisp/sbcl
> ./arch/sparc/64ul/package.mask:dev-lisp/sbcl
The flags are masked in arch/base:
$ find . -name 'use.mask' -exec grep -E '^(clisp|clozurecl|clozurecl64|cmucl|ecls|gcl|sbcl)\b' {} +
./features/musl/use.mask:sbcl
./arch/base/use.mask:clisp
./arch/base/use.mask:clozurecl
./arch/base/use.mask:cmucl
./arch/base/use.mask:ecls
./arch/base/use.mask:gcl
./arch/base/use.mask:sbcl
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2023-07-23 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 9:20 [gentoo-dev] are there any lisps in the default/linux/amd64/17.0/musl profile? Andrey Grozin
2023-07-23 9:26 ` Ulrich Mueller [this message]
2023-07-23 9:41 ` Andrey Grozin
2023-07-23 10:11 ` Ulrich Mueller
2023-07-23 10:14 ` Ulrich Mueller
2023-07-23 10:28 ` Andrey Grozin
2023-07-24 0:13 ` Violet Purcell
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=uy1j7geqn@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=grozin@woodpecker.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