On Monday 24 March 2008, Alon Bar-Lev wrote:
> On 3/24/08, Mike Frysinger <[EMAIL PROTECTED]> wrote:
> > Diego and i were talking ... we're going to go with USE=filecaps because
> > it's so new and doesnt require the libcap library in order to work at
> > runtime. probably be worthwhile to put together a little eclass of
> > functions to make people's lives easier ...
>
> Great!!!
> You write eclass, me start patching ebuilds and open bugs against
> maintainers :)

eclass wrapping will also allow us to abstract away the fun OS details, but 
we'll start with linux for now.

how much do we want to help the user ?  if they have USE=filecaps, then dont 
perform any checking ?  we'll need a kernel with file capabilities turned on, 
otherwise the prog wont work unless it's setuid ... so do we perform checking 
and drop the setuid bit on the post sly ?  i'd prefer we just make the 
filecaps desc verbose: dont set this unless you have new enough kernel with 
options enabled, otherwise things may stop working properly as non-root.
-mike

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

Reply via email to