From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] sys-meta/* to own and control /bin/{cpio,sh,tar,...} symlinks (alternatives-ish)
Date: Wed, 23 Nov 2022 21:05:47 -0500 [thread overview]
Message-ID: <Y37RewG5XxU7iDbx@eversor> (raw)
In-Reply-To: <b326f265-30fd-36a7-8f7c-5d0028bab2d3@asokolov.org>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Thu, Nov 24, 2022 at 01:32:04AM +0000, Alexey Sokolov wrote:
> > However, I tend to agree that the category should be named app-meta
> > rather than sys-meta, because chances are that non-system packages will
> > also make use of it.
> >
> > Ulrich
>
> Since these packages manage symlinks, make it app-symlink?
Mentioned this in another post, but this is limiting what would make
sense to be in there further.
app -> what if it's library alternatives?
symlink -> what if we need to use wrappers or some other solution?
Not that we ever really match categories perfectly either way, but
may as well stay generic rather than mismatch or create multiple
sub-types.
Some random ideas I had were 'alternatives', 'meta', 'select'
'select-meta', not that I thought much about it.
'meta' would essentially be like an entirely generic 'virtual' but
just without PMS restrictions. While the ones with alternatives or
select are more descriptive of what it's for without saying anything
about how we're doing it or for what type of package.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-24 2:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 7:38 [gentoo-dev] [RFC] sys-meta/* to own and control /bin/{cpio,sh,tar,...} symlinks (alternatives-ish) Michał Górny
2022-11-23 13:47 ` Michael Orlitzky
2022-11-23 14:37 ` Michał Górny
2022-11-23 14:58 ` Michael Orlitzky
2022-11-23 16:45 ` Ulrich Mueller
2022-11-24 1:32 ` Alexey Sokolov
2022-11-24 2:05 ` Ionen Wolkens [this message]
2022-11-24 2:10 ` Ionen Wolkens
2022-11-24 4:01 ` Maciej Barć
2022-11-23 15:49 ` Ionen Wolkens
2022-11-23 17:36 ` Ionen Wolkens
2022-11-24 0:14 ` Yuan Liao (Leo)
2022-11-23 13:58 ` Piotr Karbowski
2022-11-23 14:26 ` Michał Górny
2022-11-23 16:32 ` Ionen Wolkens
2022-11-23 17:48 ` Michael Orlitzky
2022-11-24 16:29 ` Michał Górny
2022-11-24 17:25 ` Maciej Barć
2022-11-24 19:01 ` Alec Warner
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=Y37RewG5XxU7iDbx@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