We want to stop systemd from being added to docker images, because of rpm requiring systemctl.

[Vít Ondruch]

Dne 2.5.2014 16:29, Matthew Miller napsal(a):
> On Fri, May 02, 2014 at 03:50:36PM +0200, Vít Ondruch wrote:
>>>> Note that just dropping systemd from your images might not be the best
>>>> choice, as you then have no owners for a lot of drop-in dirs, which made
>>>> be bad for verifying the software installed in the container images...
>>> Yeah, I was just talking about that with some people. Maybe those dirs
>>> should be moved to 'filesystem'?
>> I hope that you are speaking about 'systemd-filesystem' not
>> 'filesystem'. 'filesystem' package should not be dumping ground.
> It already kind of is a dumping ground. :)

Unfortunately I have to agree on this point, but please do not use it as 
an excuse. Rather, It should be cleaned up.

>
> I think it comes down to how common the requirement is. Since the
> directories in question are used by a huge number of packages it might make
> sense to put them in the general package rather than making a new
> subpackage.

May be we should deploy some RPM generator, which would generated 
dependencies on -filesystem subpackages, if their amount should be of 
concern.

Also, it would be beauty, if RPM could use these -filesystem packages 
during build of packages (just dreaming :).

Vít