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: Re: [gentoo-dev] [PATCH 2/2] install-qa-check.d: allow acct-user home directories under /home.
Date: Mon, 20 Jan 2020 19:22:47 -0500	[thread overview]
Message-ID: <1cd441eb-eec3-730a-ee23-897b41f6a050@gentoo.org> (raw)
In-Reply-To: <50957295.loJbHFhv61@porto>

Let it die =) I'm not going to apply the patch; it's there if someone
else decides that it's the least-bad solution to this problem.


On 1/20/20 6:57 PM, Andreas K. Huettel wrote:
> 
> Why *isn't* some /var/lib/... possible here?

It is, the question is how many backflips we should be doing to avoid
putting what is practically and factually a home directory in /home. I
have a few of these packages. I will echo ulm's sentiment that it's just
awful to put them all in

  /var/lib/user1-home
  /var/lib/user2-home
  ...

rather than /home/user1 and /home/user2.

That's also second-guessing the administrator, whose home directory
policies for e.g. backups very likely apply to the home directories I'm
creating. (Keep in mind that I'm only talking about exceptions for very
special packages that install a system user that will also be used by a
human or that stores per-user configuration. And the exception is only
for the keepdir file.)

Home directories in /home were also allowed with user.eclass, which
means that we now hit a roadblock updating those accounts to GLEP81.


> 
> I mean, user configuration works perfectly fine there, even if you have to 
> log in. And the purpose of the account is closer to, say, root (with its 
> nonstandard home directory location) than a normal user.
> 
> I've seen all possible site-specific changes to /home layout, including, 
> e.g., 
> * /home/server1/username
> * /home/large/username
> * /home/u/username
> ...
> which would all get somehow messy if a system account with a fixed path is 
> forced in there.
> 

Sure, but is having them scattered across BOTH /home AND /var/lib less
messy? We're picking a default, and with GLEP81, the people who do this
could move it to /home/u/${PN} with an overlay ebuild; whatever makes
them happy. For everyone else, it's a good default.


  reply	other threads:[~2020-01-21  0:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20  3:43 [gentoo-dev] [PATCH 0/2] allow acct-user home directories in /home Michael Orlitzky
2020-01-20  3:43 ` [gentoo-dev] [PATCH 1/2] install-qa-check.d: disallow "nix" and "gnu" as top-level paths Michael Orlitzky
2020-01-20  5:33   ` Michał Górny
2020-01-20  3:43 ` [gentoo-dev] [PATCH 2/2] install-qa-check.d: allow acct-user home directories under /home Michael Orlitzky
2020-01-20  5:35   ` Michał Górny
2020-01-20 23:57   ` Andreas K. Huettel
2020-01-21  0:22     ` Michael Orlitzky [this message]
2020-01-21  5:25       ` Michał Górny
2020-01-20  7:02 ` [gentoo-dev] [PATCH 0/2] allow acct-user home directories in /home Ulrich Mueller
2020-01-20 14:20   ` Michael Orlitzky
2020-01-20 14:50     ` David Seifert
2020-01-20 15:20       ` Michael Orlitzky
2020-01-20 18:39         ` Michał Górny
2020-01-20 18:52           ` Michael Orlitzky
2020-01-20 18:01     ` Ulrich Mueller
2020-01-20 18:15       ` Michael Orlitzky
2020-01-20 22:08     ` Alec Warner
2020-01-20 23:07       ` Michael Orlitzky
2020-01-21 18:24         ` Robin H. Johnson
2020-01-21 11:44     ` Jaco Kroon
2020-01-21 14:57       ` 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=1cd441eb-eec3-730a-ee23-897b41f6a050@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