FS#6062 - files in the "filesystem" package should belong to somewhere else
Attached to Project:
Arch Linux
Opened by Andrea Garbarini (garba) - Saturday, 23 December 2006, 11:13 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 15:08 GMT
Opened by Andrea Garbarini (garba) - Saturday, 23 December 2006, 11:13 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 15:08 GMT
|
Details
Actually, I can't understand what the purpose of this
package is. What's worse this package contains files which
should belong to somewhere else, pick nsswitch.conf and
resolv.con for example: these files are parsed by the name
switch service and the resolver libs, and since these libs
come in the glibc package, that's the package these files
should belong to. I can't understand why people insist on
thinking of these files as "special". For consistency's sake
I would suggest to tidy this package up a little. Regards,
andre
|
mkdir -p var/{..,games}
#Allow setgid games to write scores:
chmod 775 ${startdir}/pkg/var/games
chown root:50 ${startdir}/pkg/var/games
in order for people who install gnome, and play games to get their scores written down an extra directory was added to this package cause it was considered an easy solution. isnt there a way for these kind of additions to be part of the actual packages that use them?
this package needs an overhaul, even despite that
My way of thinking and approaching this might be totallly wrong here but just as an example: /var/lib/pacman is provided by filesystem but it is also created by pacman. Why create it two times?
The way i see it the filesystem package should provide a basic directory tree for / (bin,boot,..,var), any other needed directories inside them that are absolutely needed eg. some /var dirs and configuration files for /etc that provide a customisation for base packages.
But as i said before the way i appoach this might be totally off.
Last, is /etc/arch-release still needed? i remember some discussions at some previous time that it was only left there for some specific reason i seem not to remember at the moment. is the reason still valid?
I feel that we should keep these config files in filesystem. It's a convenience package.
Also, I agree that games shouldn't be there, but how do we fix this globally? Where should this be moved to?
I also believe filesystem should have no dependencies whatsoever to ensure it gets installed first- otherwise the package is useless as all dirs will have been created anyways (possibly with wrong permissions). I think a post_upgrade function is ok, but post_install should be eliminated and the coreutils and sh deps removed.
Finally, I think there have to be a few files present- I'm not sure where else you would put motd, issue, etc.
if you accept my logic then the same goes for /var/abs (part of abs) and probably most subdirectories of the directores lying in the root tree!
well , the /var/games dir was added to solve this bug http://bugs.archlinux.org/task/6912 . emacs also uses this dir but in contrast to gnome-games this dir is part of the package list.
i guess the package is ok if u exclude that and /var/lib/pacman and /var/abs dirs, the already known manpage dirs location ofc, and as u said all conf files stay
In all seriousness, though, with games being acceptable under the FHS, the only really actionable stuff here is removing the pacman directories, is that correct?