| 1 |
On 21/05/2013 05:03, Daniel Campbell wrote: |
| 2 |
> That's missing the point. If you don't run systemd, having unit files is |
| 3 |
> pointless. Thankfully there's INSTALL_MASK and whatnot, but that seems |
| 4 |
> like a hack instead of something more robust. Why include systemd unit |
| 5 |
> files (by default, with no systemd USE flag, thanks to the council...) |
| 6 |
> on a system that's not using it? 154 files isn't negligible unless |
| 7 |
> you're flippant with your system and don't care about bloat. Unused |
| 8 |
> software sitting around *is* a waste of disk-space. |
| 9 |
> |
| 10 |
> Some people (like myself) came to Gentoo to avoid putting systemd on |
| 11 |
> their systems and to make use of the great choice that Gentoo allows. |
| 12 |
> This push to make systemd a "first level citizen" or whatever reeks of |
| 13 |
> marketing. If there is desire among users for unit files, they can |
| 14 |
> contact upstream or maintain their own set of unit files. It's not like |
| 15 |
> they're hard to write. |
| 16 |
> |
| 17 |
|
| 18 |
<amused long-term user chipping in> |
| 19 |
|
| 20 |
This is such a weak argument it's quite laughable. |
| 21 |
|
| 22 |
I don't like gnu info files. Neither me nor anyone I know can figure out |
| 23 |
how to drive info. So, let's rip all the info files out of every |
| 24 |
package; leaving the 3 users who do know info free to grab their copies |
| 25 |
from upstream. I mean it's not like it's hard or anything, and info |
| 26 |
files are easy to write. |
| 27 |
|
| 28 |
Daniel, you should just get over it. Having choices means you let the |
| 29 |
other guy have his choices too. Sometimes that means you have to let |
| 30 |
that guy have a little bit of his infra lying around so his choice is |
| 31 |
possible. And no-one ever said having choices means your exact personal |
| 32 |
preferences wrt every little thing will be baked in. |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Alan McKinnon |
| 37 |
alan.mckinnon@×××××.com |
Archives