Re: [atomic-devel] Python-pyudev instead of storaged

2016-06-21 Thread Marius Vollmer
Colin Walters writes: > On Thu, Jun 16, 2016, at 04:37 AM, Marius Vollmer wrote: >> Hi, >> >> if I understand things right, adding storaged as a dependency to >> cockpit-docker is not acceptable. Can I add python-pyudev instead? >> >> Incidentall, what about NetworkManager-team? > > We have a f

Re: [atomic-devel] Python-pyudev instead of storaged

2016-06-21 Thread Colin Walters
On Thu, Jun 16, 2016, at 04:37 AM, Marius Vollmer wrote: > Hi, > > if I understand things right, adding storaged as a dependency to > cockpit-docker is not acceptable. Can I add python-pyudev instead? > > Incidentall, what about NetworkManager-team? We have a few conflicting masters here: -

Re: [atomic-devel] Python-pyudev instead of storaged

2016-06-16 Thread Marius Vollmer
Stef Walter writes: > About pyudev ... I would suggest that functionality we're starting to > use it for (such as monitoring for storage devices, and listing their > properties) should go into the 'atomic storage' subcommand. If it needs > python-pyudev to make that work, then it makes sense to i

Re: [atomic-devel] Python-pyudev instead of storaged

2016-06-16 Thread Stef Walter
On 16.06.2016 10:37, Marius Vollmer wrote: > Hi, > > if I understand things right, adding storaged as a dependency to > cockpit-docker is not acceptable. Can I add python-pyudev instead? > > Incidentall, what about NetworkManager-team? So long term, the goal for Cockpit should be to run more in

[atomic-devel] Python-pyudev instead of storaged

2016-06-16 Thread Marius Vollmer
Hi, if I understand things right, adding storaged as a dependency to cockpit-docker is not acceptable. Can I add python-pyudev instead? Incidentall, what about NetworkManager-team?