Re: Should packages really own their config files???

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

 



On Sat, Sep 02, 2006 at 12:14:49PM -0500, Rex Dieter wrote:
> On Sat, 2 Sep 2006, Jesse Keating wrote:
> 
> > On Sat, 2006-09-02 at 18:03 +0200, Axel Thimm wrote:
> >> Isn't this handled in some guidelines? If not shouldn't it?
> >
> > I thought we had a rule about creating files in %post or whatnot and not
> > owning them.  I could be wrong, but I check for that when I review
> > packages.  IMHO any file a package creates on the file system at install
> > time should be owned or ghosted by that package.
> 
> I argued for such a rule, but others pointed out examples where this is
> not always/generally a good idea, so the proposal did not have the
> support to pass.

Were the examples for certificate/ssh keys only? I don't really meant
these with "config files". Are there any arguments against owning
config files but certifcates/ssh keys?
-- 
Axel.Thimm at ATrpms.net

Attachment: pgpHM2ZYEn326.pgp
Description: PGP signature

--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux