| Summary: | net-p2p/amule ebuild should not create /home/p2p | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Roman Polach <rpolach> |
| Component: | New packages | Assignee: | Gentoo net-p2p team <net-p2p> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | trivial | ||
| Priority: | Lowest | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Roman Polach
2006-10-02 16:34:31 UTC
(In reply to comment #0) > net-p2p/amule (and e.g. net-p2p/mldonkey) ebuild > in pkg_preinst() enewuser creates new user with /home/p2p home dir. I can not confirm this behaviour. What's the version of amule in question, and what's your USE flags for amule (e.g. "equery uses amule")? If it did that, it would be bad for other reasons, like the common situation of /home being an NFS automount, in which case root would not be able to create new directories there. my USE flags are "amuled" on one machine and "remote" on another...
I use amule-2.1.3...
this piece of code is from amule-2.1.3 ebuild, it shows enewuser command
causing the problem clearly:
pkg_preinst() {
if use amuled || use remote; then
enewgroup p2p
enewuser p2p -1 -1 /home/p2p p2p
fi
}
in 2.1.2 there is similar code with only formatting difference:
pkg_preinst() {
if use amuled || use remote; then
enewgroup p2p
enewuser p2p -1 -1 /home/p2p p2p
fi
}
|
