[systemd-devel] Factoring out initctl support

[Daniel Mack]

On 04/15/2016 10:47 PM, Michael Biebl wrote:
> 2016-04-15 19:33 GMT+02:00 Daniel Mack <daniel at zonque.org>:
>> On 04/15/2016 07:03 PM, Mike Gilbert wrote:
>>> On Fri, Apr 15, 2016 at 11:43 AM, Daniel Mack <daniel at zonque.org> wrote:
>>>> On 04/15/2016 03:55 PM, Mike Gilbert wrote:
>>
>>>>> I'm happy to move it if others want to utilize it. I will need someone
>>>>> to set me up with access to push the code, however.
>>>>
>>>> Great, will do. What's your GitHub handle?
>>>
>>> I'm floppym on github.
>>>
>>
>> Thanks - you're now the admin of this new repository:
>>
>>   https://github.com/systemd/systemd-initctl/
>>
>> I'm happy to push the client code there once you migrated the project.
>>
>>
>> However, I'd still like to have an Ack from Michael Biebl on the
>> downstream integration of this new repository.
> 
> Well, I guess I already explained our situation. We still need
> /dev/initctl in Debian, so ripping that out means we have to provide
> that some other way.
> I'm not sure if a separate package (large overhead) or simply
> reverting the removal is the better option here.

Including the built results of systemd-initctl into your .deb packet is
not a solution? Making that an extra package causes too much trouble, I
totally agree.

> I can only reiterate what I said before: the code is pretty isolated
> so I don't see how that causes upstream any maintenance headaches and
> I would volunteer to take care of any issues that are caused by that
> code.
> Personally I would prefer it, if we added a configure switch. This
> would be off by default so we wouldn't advertise legacy cruft by
> default but it would make it easier for distros which need to maintain
> that level of compat support.

This is an exercise in making the code base smaller and dropping support
for some legacy, while still keeping support around via external
packages. And initctl is a low-hanging fruit, hence the idea.


Thanks,
Daniel