Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-triggers: make system-accounts behave in altroots
Date: Tue, 15 Sep 2020 21:32:15 +0200	[thread overview]
Message-ID: <20200915193215.pVptcGWdycytbowmdBYLhIuciSLZ2F6wH8LzqQdhkhk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24812@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/24812#issuecomment-692931476

Comment:
@the-maldridge I don't believe these changes are any less robust for systems using remote directories than the current state. It is using the proper tools anyway.

Even so, there is the argument that these shouldn't be supported, given that these are system accounts and should be available in all situations.

We have discussed the possibility of bringing the `system_{account,group}` functionality into XBPS itself, but I believe it would also break in the alternate root case with remote directory, due to the host system's setup not being necessarily the same as the target system. More importantly, someone using `xbps.static` on a glibc system would lack the extra functionality implemented by glibc, if I understand things correctly.

  reply	other threads:[~2020-09-15 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 18:37 [PR PATCH] " ahesford
2020-09-15 19:32 ` ericonr [this message]
2020-09-17  1:04 ` [PR PATCH] [Updated] " ahesford
2020-09-17  1:15 ` ahesford
2020-09-17  5:18 ` the-maldridge
2020-09-18 13:44 ` [PR PATCH] [Updated] " ahesford
2020-09-18 14:00 ` [PR PATCH] [Closed]: " ahesford

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=20200915193215.pVptcGWdycytbowmdBYLhIuciSLZ2F6wH8LzqQdhkhk@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).