public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [PATCH v2 0/4] acct-{user,group}.eclass: make user/group names writable
Date: Thu,  9 May 2024 16:41:55 -0400	[thread overview]
Message-ID: <20240509204159.18123-1-mjo@gentoo.org> (raw)

Support changing the user/group name of GLEP81 packages. This is
sometimes required in overlays because package naming restrictions
prohibit valid user/group names from being package names.

We drop "readonly" from the eclasses, and use PN instead of
ACCT_{USER,GROUP}_NAME to construct the make.conf overrides.

Changes in v2:

  - Two spaces after a period.
  - Use PN directly for override names

Michael Orlitzky (4):
  acct-user.eclass: make ACCT_USER_NAME writable
  acct-group.eclass: make ACCT_GROUP_NAME writable
  eclass/acct-user.eclass: use $PN to construct make.conf override vars
  eclass/acct-group.eclass: use $PN to construct make.conf override vars

 eclass/acct-group.eclass | 18 ++++++++++--------
 eclass/acct-user.eclass  | 22 ++++++++++++----------
 2 files changed, 22 insertions(+), 18 deletions(-)

-- 
2.43.2



             reply	other threads:[~2024-05-09 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 20:41 Michael Orlitzky [this message]
2024-05-09 20:41 ` [gentoo-dev] [PATCH v2 1/4] acct-user.eclass: make ACCT_USER_NAME writable Michael Orlitzky
2024-05-09 20:41 ` [gentoo-dev] [PATCH v2 2/4] acct-group.eclass: make ACCT_GROUP_NAME writable Michael Orlitzky
2024-05-09 20:41 ` [gentoo-dev] [PATCH v2 3/4] eclass/acct-user.eclass: use $PN to construct make.conf override vars Michael Orlitzky
2024-05-09 20:41 ` [gentoo-dev] [PATCH v2 4/4] eclass/acct-group.eclass: " Michael Orlitzky
2024-05-13 13:26 ` [gentoo-dev] [PATCH v2 0/4] acct-{user,group}.eclass: make user/group names writable Michael Orlitzky

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=20240509204159.18123-1-mjo@gentoo.org \
    --to=mjo@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