| 1 |
On 16/11/16 06:16 PM, William Hubbs wrote: |
| 2 |
> On Wed, Nov 16, 2016 at 06:09:59PM -0500, Ian Stakenvicius wrote: |
| 3 |
>> On 16/11/16 03:21 PM, William Hubbs wrote: |
| 4 |
>>> |
| 5 |
>>> I can make the service scripts call the systemd-tmpfiles service if it |
| 6 |
>>> is available or if not call the opentmpfiles implementation. |
| 7 |
>>> |
| 8 |
>>> I'm not sure whether it is worth having a separate package for the |
| 9 |
>>> service scripts in this case. |
| 10 |
>> |
| 11 |
>> That would depend on where the service scripts are sitting, I guess -- |
| 12 |
>> do you mean here that openrc will keep its current tmpfiles.dev and |
| 13 |
>> tmpfiles.setup scripts? If that's the case wouldn't openrc need to |
| 14 |
>> RDEPEND or PDEPEND on virtual/tmpfiles ? |
| 15 |
> |
| 16 |
> No, those scripts will be removed from OpenRC. If you grep through |
| 17 |
> OpenRC, you will see that once they are removed, they are never actually |
| 18 |
> referred to by any other services that are part of OpenRC. |
| 19 |
> |
| 20 |
> The scripts will be put in opentmpfiles and that ebuild will install |
| 21 |
> them. |
| 22 |
> |
| 23 |
> William |
| 24 |
> |
| 25 |
|
| 26 |
Then we're back to the exact same issue. opentmpfiles won't be |
| 27 |
installed if systemd is installed, so the scripts won't get installed. |
Archives