From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [Rehash] Renaming "PMS" into "EAPI"
Date: Sun, 10 Nov 2024 10:44:39 +0000 [thread overview]
Message-ID: <b8d6f6b229cb2e3136b4d85ea93dd04c34df3b22.camel@gentoo.org> (raw)
In-Reply-To: <u8qtrhd9s@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
On Sun, 2024-11-10 at 06:24 +0100, Ulrich Müller wrote:
> > > > > > On Sun, 10 Nov 2024, Arsen Arsenović wrote:
>
> > I agree. The name "EAPI" seems okay even if, strictly speaking,
> > incorrect.
>
> So we would replace an accurate name by an incorrect one, and we would
> lose the distinction between the name of the spec and the name of the
> ebuild API.
>
> I was briefly thinking about something like "Ebuild specification".
> Then again, while most of PMS is about the ebuild format, some parts
> of it are about other aspects of the repository (e.g. profiles and
> metadata cache) or the package manager.
>
> > That's also how we reference the applicable version of the
> > specification in ebuilds.
>
> That's not entirely correct either. For example, an ebuild may reference
> EAPI 7 which is defined in PMS version 8_p20210613.
>
> > WRT whether "PMS" is a bad joke, I have no reason to believe it isn't
> > (even if never said out loud), nor that it is, but I do know that, in
> > either case, it does cause (at least) confusion.
>
> Most acronyms have multiple meanings. I don't think that the full term
> "Package Manager Specification" causes confusion.
How about referring to it as PM Spec? Shortened to pmspec? It's just as easy
to say.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2024-11-10 10:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:25 [gentoo-project] [Rehash] Renaming "PMS" into "EAPI" Michał Górny
2024-11-08 15:36 ` Maciej Barć
2024-11-08 17:55 ` Ulrich Müller
2024-11-09 23:40 ` Arsen Arsenović
2024-11-09 22:37 ` James Le Cuirot
2024-11-09 23:38 ` Arsen Arsenović
2024-11-10 5:24 ` Ulrich Müller
2024-11-10 10:44 ` James Le Cuirot [this message]
2024-11-10 14:21 ` Matthew Marchese
2024-11-10 14:22 ` Maciej Barć
2024-11-10 14:32 ` Sam James
2024-11-10 14:43 ` Rich Freeman
2024-11-10 15:50 ` Ulrich Müller
2024-11-10 18:03 ` Andreas K. Huettel
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=b8d6f6b229cb2e3136b4d85ea93dd04c34df3b22.camel@gentoo.org \
--to=chewi@gentoo.org \
--cc=gentoo-project@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