Re: [PATCH] make capabilities support optional

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 23 April 2010 15:12:33 Chuck Lever wrote:
> If we really do need to drop libcap for some configurations, then such a
> change should be thoroughly tested in those environments.  Some features
> won't always work without libcap, and appropriate warnings should be
> added to man pages and/or should be displayed by statd.

there should be appropriate documentation regardless.  current nfs-utils lists 
no information at all in ChangeLog/NEWS/README/INSTALL or any other document 
explaining why/what/how libcap is needed/used.  you cant do documentless dumps 
on distro maintainers and expect them to "just know" what is going on.  this 
isnt the first time the nfs related packages suddenly started requiring new 
libraries out of the blue when in reality things could be done optionally, nor 
is this the first patch ive sent to try and address what appears to be 
unnecessarily hard deps.  kerberos readily comes to mind.

i'd point out that from a distro POV, the DAEMON section of the top level 
README is single handily the best thing added in a long time.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux