Summary: | sys-apps/portage: specifying home directory ownership/permissions for system accounts is useless | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Maxim Kammerer <mk> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | leho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 53269 | ||
Bug Blocks: |
Description
Maxim Kammerer
2011-12-25 04:22:28 UTC
Mike Frysinger's November 23 message "restricting phases where enew{user,group} is allowed" <http://archives.gentoo.org/gentoo-dev/msg_ed43ed0df212ea26ef953fb061e9e860.xml> is relevant to this. The change he committed does not conflict with anything described in comment #0, but he does indicate that he would like to move away from using pkg_setup for user creation (unless the upstream build system requires the user to exist for compilation to work properly). If you are already auditing builds and/or rearranging their user management, pushing user creation down to pkg_preinst where possible would help with his long term plan. In the tor case described above, you could then have pkg_preinst handle everything related to /var/lib/tor: pkg_preinst() { [[ -e "${ROOT}/var/lib/tor" ]] local had_home=$? enewgroup tor enewuser tor -1 -1 /var/lib/tor tor if [[ "$had_home" -ne 0 ]]; then chgrp tor "${ROOT}/var/lib/tor" chmod 0750 "${ROOT}/var/lib/tor" fi } *** This bug has been marked as a duplicate of bug 141619 *** |