| 1 |
On Sat, Dec 8, 2012 at 8:53 AM, Tomáš Chvátal <tomas.chvatal@×××××.com> wrote: |
| 2 |
> Does it really have to be useflag? Can't we simply just install the |
| 3 |
> file every time like we do with everything else? Logrotate/normal |
| 4 |
> initscripts/etc/etc. |
| 5 |
> |
| 6 |
> There should be no issue with that if we install the service files |
| 7 |
> every time, they just take few kbs in /etc/ |
| 8 |
|
| 9 |
For unit files I'd tend to agree. |
| 10 |
|
| 11 |
However, these did not control the installation of unit files (unless |
| 12 |
I missed something in there). Many controlled whether the package |
| 13 |
used consolekit vs systemd, so unless somebody defines a common API |
| 14 |
between them and a virtual a USE flag makes sense. |
| 15 |
|
| 16 |
I'm not as certain about the socket file use case. If the use flag is |
| 17 |
triggering both the installation of a socket file and also the |
| 18 |
disabling of something else it might be necessary. On the other hand, |
| 19 |
if it is just toggling between installing the socket file for systemd |
| 20 |
vs under xinetd.d then it might be safe to just install both since I |
| 21 |
doubt systemd users are likely to also run xinetd. That might not be a |
| 22 |
safe assumption - during the transition they might end up running |
| 23 |
both. |
Archives