Bug 246021 - emerging nfs-utils does not register /etc/exports as belonging to it if it already exists.
Bug#: 246021 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: net-fs@gentoo.org Reported By: smallnow@gmail.com
Component: Applications
URL: 
Summary: emerging nfs-utils does not register /etc/exports as belonging to it if it already exists.
Keywords:  
Status Whiteboard: 
Opened: 2008-11-08 01:03 0000
Description:   Opened: 2008-11-08 01:03 0000 
emerging nfs-utils with no /etc/exports, a default exports file is made and
$ qfile /etc/exports
shows nfs-utils.
Now emerge nfs-utils again when there already exists an /etc/exports, qfile
/etc/exports commands show nothing (an orphaned file).
This is wrong. 
One obvious reason is that it inconsistent with how other packages work.

I tested this with 2 versions: 1.1.3 and the latest 1.1.4.



Reproducible: Always

------- Comment #1 From Wormo 2008-11-09 05:36:58 0000 ------- 
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?

------- Comment #2 From SpanKY 2008-11-09 07:19:03 0000 ------- 
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