On Sun, Sep 14, 2014 at 11:15:13PM +0200, Nowaker wrote:
> At this point /var/lib/pacman/local defines the current state of /usr.
> It's not "variable" - you write to /var/lib/pacman/local if and only if
> you write to /usr. The description of /usr on wiki perfectly describes
> why /var/lib/pacman/local really belongs there:
So, files in (now) /usr/lib/pacman/local contain filelists of packages, yes? If
you wipe /var, lots of packages will have missing files...
> - move /var/lib/pacman/local/ to /usr
> - move the default pacman.conf and mirrorlist to /usr/share
> - provide tmpfiles.d to copy those files to /etc
What about pacman keyring? Also note that your custom keys should be packaged
as well and resigned on-boot.
> If I'm not mistaken, /usr/share and tmpfiles.d are really trivial and
> wouldn't affect users in any way. That'd be a few additional files
> somewhere in the filesystem without any effect on existing machines. Or
> I'm wrong?
This is madness. I remember sometime ago there was a witchhunt against daemons
that write to /etc (cups is the worst offender). So why is it OK for systemd to
do so? I personally don't want systemd to come anywhere near my /etc. Please
package the tmpfiles.d/sysusers stuff with virtkick or whatever, but not with
pacman.
Cheers,
--
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4
C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Attachment:
pgpERvI9K_0EU.pgp
Description: PGP signature
