| 1 |
On 28/02/14 13:15, Patrick Lauer wrote: |
| 2 |
> On 02/27/2014 09:08 PM, Anthony G. Basile wrote: |
| 3 |
>> Hi everyone, |
| 4 |
>> |
| 5 |
>> I'm putting the call out there for any agenda items for the next Council |
| 6 |
>> meeting, which will be held on March 11, 2014 at 1900 UTC. This is |
| 7 |
>> short notice but we got off track because of FOSDEM and we're going to |
| 8 |
>> try to get back on track. |
| 9 |
>> |
| 10 |
>> So far, the only item is final ratification of glep 63 [1]. |
| 11 |
> Since it's still a bit cold I'd like to start a nice fire to warm us up: |
| 12 |
> |
| 13 |
> I'd like QA and Council to figure out how much we care about FHS. |
| 14 |
> |
| 15 |
> My main complaint is some projects (including e.g. systemd and |
| 16 |
> apparently now also udev) storing config files in /lib and/or /usr/lib. |
| 17 |
> |
| 18 |
> From FHS' point of view this is totally wrong, config files go to /etc |
| 19 |
> Only libraries should be in /lib. |
| 20 |
|
| 21 |
Wow. |
| 22 |
What about libtool .la text files? |
| 23 |
What about kernel modules? |
| 24 |
What about the genereted modules.* data in /lib/modules/$version/ which |
| 25 |
are used in early boot by eg. kmod-static-nodes? |
| 26 |
What about the binaries of OpenRC in /lib/rc, they aren't libraries? |
| 27 |
And what about vendor modprobe.d files in /lib/modprobe.d? |
| 28 |
I could continue this all day. I'm just trying to point out "Only |
| 29 |
libraries should be in /lib." is complete bs and does not work. |
| 30 |
Does FHS really articulate it the way you said it, "Only libraries |
| 31 |
should be in /lib." or was that your own interpretation of it? |
| 32 |
|
| 33 |
I'm not really expecting an answer as I'm already convinced FHS is so |
| 34 |
badly outdated it's sad it doesn't suit |
| 35 |
modern systems. |
| 36 |
I hope they will catch up at some point. |
| 37 |
|
| 38 |
- Samuli |
Archives