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

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

 



On Sat, 2006-09-02 at 18:14 +0200, Axel Thimm wrote:
> 
> The file is not created by %post. Currently it is created by anaconda,
> which is a remnant of old times (a safety measure of making sure rpm
> behaves multilib).

> The target would be for anaconda to not have to touch /etc/rpm/config
> at all leaving it completely to the user's discretion. But still that
> file is unowned. 

If anaconda creates it, and nothing else owns it, anaconda should become
the owner, or it should be packaged up by rpm.  If anaconda doesn't
touch it, then it shouldn't be packaged at all.  It would be like the
user created files in /etc/httpd/conf.d/ or any other such thing.  /etc
isn't rpm's playground alone, there could be many files in there not
owned by a package once the system is used for a while.

-- 
Jesse Keating RHCE      (geek.j2solutions.net)
Fedora Legacy Team      (www.fedoralegacy.org)
GPG Public Key          (geek.j2solutions.net/jkeating.j2solutions.pub)

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

--
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