From: Daniel Campbell <zlg@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2015-10-11
Date: Sun, 18 Oct 2015 15:28:28 -0700 [thread overview]
Message-ID: <56241D0C.9070808@gentoo.org> (raw)
In-Reply-To: <20151018232807.6773731d.mgorny@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/18/2015 02:28 PM, Michał Górny wrote:
> On Sun, 18 Oct 2015 22:58:31 +0200 Ulrich Mueller <ulm@gentoo.org>
> wrote:
>
>> Following up to this. I think the choice is between the two
>> extremes of keeping the status quo and of changing all non-FHS
>> locations, or some intermediate solution.
>>
>> 1. Keep status quo:
>>
>> /usr/games/bin games binaries /usr/games/lib* games
>> libraries /usr/share/games static games data /etc/games games
>> configuration /var/games variable game data
>> /var/log/games games logs
>
> This is no longer 'status quo', rather 'past status quo' which is
> slowly removed in favor of whatever upstream uses.
>
>> 2. Change all locations that are not conforming to FHS 3.0:
>>
>> /usr/bin games binaries Rationale: The FHS has
>> /usr/games as an optional directory for binaries, but we cannot
>> use it because it is blocked by the current directory layout
>> with /usr/games/{bin,lib*}.
>>
>> /usr/lib* games libraries
>>
>> /usr/share static games data Rationale: The FHS also
>> allows an optional /usr/share/games but its description says
>> "Static data files for /usr/games". So if the binaries are
>> installed in /usr/bin then (as I read it) the data should go to
>> /usr/share (i.e., to /usr/share/${PN} really).
>
> I'd say we shouldn't take FHS this strongly, and use whatever
> upstream uses. If upstream uses /usr/share/games, so be it. If it
> uses /usr/share directly, so be it. Otherwise, we end up patching
> stuff and unnecessary patching is no fun at all. I still remember
> how much code I had to patch to make random games comply to
> 'gentoo' locations.
>
>> /etc games configuration
>>
>> /var/games variable game data Rationale: FHS section
>> 5.7.: "Any variable data relating to games in /usr should be
>> placed here." This could also be used for logs previously placed
>> in /var/log/games, when for some reason they cannot got to
>> /var/log (but AFAICS it would affect only two packages in the
>> tree).
>
(Replying normally and CCing the list since Tbird didn't give me a
"Reply to List" option)
I'm in favor of sticking to upstream where possible. Keeping a bunch
of patches around would make the already-arduous work of games
maintenance even worse. I can appreciate the interest in keeping games
in one place, though, since some users would want their games to
perform well and put a specific path on an SSD or something. The key
part, imo, is whatever we decide on is realistic to implement and
doesn't ruin the filesystem structure. Some upstreams could be
considered less-than-ideal in their care (or lack thereof) when
dealing with directories and install locations.
Maybe we should take an inventory of some common games and determine
where upstream wants to put them in the first place.
- --
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWJB0LAAoJEAEkDpRQOeFwxIcP/Rt8/zUejhuCgVatnD+KFhqg
lNrTgkesuTRCl1Q5c2Fyjs6XaXoGxv0G+eVL3V0zlM8haHNY6bJL4+XnnthBD1qI
WyRT07xpFPbNPCXiBaYb2z4EaYugMjugHgmpYg6JFny4YNvOsTHGKDxwTqHegdB0
qmzkOVKj2k6gYGHs10mRHpVuDFF4kAvahafkKC41moD1LNcoJLzVALwT/UwZlB6s
hvWuwYiYcfOuDbyQXmYg5zuWP+77lfcLh1oUtcTzJW/L7H2EQCF4d+aREP1mUEnG
5q7LvIIUsdNyV8L7u0CifoHezK7Er23fn5LnSgvYXgBq0n+Efx9HWqSgcb/fuSfI
qTi4Gs6LMDt0PSRyetrI0/0DcthfVzsDuHyRxdiEMNHvZPJsRimNqm/6gm2B+n3h
/nglbx3IHLp0t0jkwHNA2DyGwFROlf59OQyPHlJ58gR7Mu5TbzoV9Ep5GJrE3pSg
31zkkoefLVGOgTWimsvKMbEZVqI0iA+3fQoJqrH3dXT756vfs45Pm0bFcjL+V93c
WWZrK+UByPTb2Xww6FVvnx04n+k/UQXus8FDRhcuiCqvZ2IsPDx4QUSsr0oylCMe
jDsnFktRWOPzvKzoRkW2FSfWRkR/nR2hYQVJRaFzHF07lOuYkAYnOIJ1GaEtz88U
yXRylZIf1mf4YsOl1GD3
=6avU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-10-18 22:28 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 14:01 [gentoo-project] Call for Agenda Items -- Council Meeting 2015-10-11 Andreas K. Huettel
2015-09-30 18:15 ` Michał Górny
2015-09-30 19:10 ` Ulrich Mueller
2015-09-30 19:22 ` Michał Górny
2015-09-30 19:39 ` Ulrich Mueller
2015-09-30 19:47 ` Michał Górny
2015-09-30 20:05 ` Ulrich Mueller
2015-09-30 20:12 ` Michał Górny
2015-10-01 13:00 ` Alexis Ballier
2015-09-30 19:45 ` Rich Freeman
2015-09-30 20:21 ` Andreas K. Huettel
2015-09-30 20:26 ` Michał Górny
2015-09-30 20:36 ` Andreas K. Huettel
2015-09-30 20:39 ` Michał Górny
2015-10-01 21:53 ` Andreas K. Huettel
2015-09-30 21:05 ` Rich Freeman
2015-10-01 12:53 ` Alexis Ballier
2015-10-01 12:55 ` Alexis Ballier
2015-10-01 19:08 ` Kristian Fiskerstrand
2015-10-01 19:14 ` Michał Górny
2015-10-01 19:14 ` Kristian Fiskerstrand
2015-10-01 19:39 ` Michał Górny
2015-10-01 19:53 ` Kristian Fiskerstrand
2015-10-02 14:42 ` Andreas K. Huettel
2015-10-02 18:22 ` Michał Górny
2015-10-03 9:40 ` Ulrich Mueller
2015-10-03 10:49 ` Michał Górny
2015-10-03 11:23 ` Alex Legler
2015-10-02 0:57 ` [gentoo-project] Project membership vs being on a mail alias: pitfalls and problems Robin H. Johnson
2015-10-02 6:49 ` Michał Górny
2015-10-05 5:47 ` [gentoo-project] Call for Agenda Items -- Council Meeting 2015-10-11 Michał Górny
2015-09-30 18:43 ` [gentoo-project] " Ulrich Mueller
2015-09-30 18:45 ` [gentoo-project] " Michał Górny
2015-10-08 12:42 ` Andrew Savchenko
2015-10-08 12:58 ` Anthony G. Basile
2015-10-08 14:09 ` Michał Górny
2015-10-08 15:01 ` Anthony G. Basile
2015-10-08 15:27 ` hasufell
2015-10-08 18:24 ` Rich Freeman
2015-10-09 1:21 ` Andrew Savchenko
2015-10-09 9:44 ` Rich Freeman
2015-10-09 10:29 ` Anthony G. Basile
2015-10-09 16:12 ` Ian Delaney
2015-10-09 19:29 ` Rich Freeman
2015-10-09 10:31 ` hasufell
2015-10-09 10:50 ` Anthony G. Basile
2015-10-09 10:58 ` hasufell
2015-10-09 11:07 ` Anthony G. Basile
2015-10-09 11:17 ` Anthony G. Basile
2015-10-09 11:23 ` hasufell
2015-10-09 11:56 ` Anthony G. Basile
2015-10-09 12:15 ` hasufell
2015-10-09 23:40 ` Andreas K. Huettel
2015-10-10 10:16 ` hasufell
2015-10-10 11:35 ` Andreas K. Huettel
2015-10-10 11:37 ` hasufell
2015-10-10 12:21 ` Fabian Groffen
2015-10-10 12:23 ` hasufell
2015-10-10 13:56 ` Andreas K. Huettel
2015-10-10 17:14 ` Dale
2015-10-10 18:56 ` Andrew Savchenko
2015-10-10 18:59 ` Ciaran McCreesh
2015-10-10 21:41 ` Rich Freeman
2015-10-17 23:14 ` Andrew Savchenko
2015-10-17 23:36 ` Rich Freeman
2015-10-18 0:33 ` Anthony G. Basile
2015-10-20 9:36 ` Alexander Berntsen
2015-10-20 10:05 ` Rich Freeman
2015-10-20 10:11 ` Alexander Berntsen
2015-10-10 19:17 ` hasufell
2015-10-10 1:41 ` Matt Turner
2015-10-08 18:30 ` Michał Górny
2015-10-09 9:35 ` Rich Freeman
2015-10-10 1:51 ` Matt Turner
2015-10-10 8:21 ` Anthony G. Basile
2015-10-09 23:38 ` Andreas K. Huettel
2015-10-10 7:21 ` Michał Górny
2015-10-10 1:44 ` Matt Turner
2015-10-08 18:48 ` Michael Orlitzky
2015-10-08 20:22 ` James Le Cuirot
2015-10-09 23:34 ` Andreas K. Huettel
2015-10-10 7:26 ` Michał Górny
2015-09-30 19:12 ` Rich Freeman
2015-10-01 18:36 ` Rich Freeman
2015-09-30 20:24 ` Manuel Rüger
2015-10-01 12:32 ` Rich Freeman
2015-10-01 13:18 ` Ulrich Mueller
2015-10-12 8:23 ` Michał Górny
2015-10-12 12:42 ` Ulrich Mueller
2015-10-18 20:58 ` Ulrich Mueller
2015-10-18 21:18 ` Rich Freeman
2015-10-18 21:49 ` Ulrich Mueller
2015-10-18 22:13 ` hasufell
2015-10-18 23:35 ` Rich Freeman
2015-10-18 21:28 ` Michał Górny
2015-10-18 21:54 ` hasufell
2015-10-18 21:56 ` Ulrich Mueller
2015-10-18 22:28 ` Daniel Campbell [this message]
2015-10-18 22:40 ` James Le Cuirot
2015-10-19 7:55 ` Michał Górny
2015-10-19 10:44 ` hasufell
2015-10-12 13:07 ` hasufell
2015-10-04 11:13 ` Michał Górny
2015-10-04 12:17 ` Rich Freeman
2015-10-07 11:58 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56241D0C.9070808@gentoo.org \
--to=zlg@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=mgorny@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox