Summary: | emerging nfs-utils does not register /etc/exports as belonging to it if it already exists. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Kelling <smallnow> |
Component: | Current packages | Assignee: | Network Filesystems <net-fs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ian Kelling
2008-11-08 01:03:21 UTC
The nfs-utils ebuild does purposefully leave /etc/exports alone if it exists, instead of using the normal mechanism of updating protected configs. However, it is not obvious _why_ it has this behavior; I'll leave it up to the maintainers to explain it... perhaps there was a historical reason that no longer applies? the /etc/exports that always gets installed is an empty file, so it didnt make sense in the past to always bug people about "upgrading" their existing file to an empty one. it still doesnt make any sense, but portage nowadays should bug you a lot less often, so i'll just drop it. http://sources.gentoo.org/net-fs/nfs-utils/nfs-utils-1.1.4.ebuild?r1=1.3&r2=1.4 |