Bug#801253: how to handle not much used feature which depends on a deprecated technology

[toogley <toogley@mailbox.org>]

Hey,

thanks a lot for your comments.

Additionally, i'll ask upstream what they think about option 1) and 3), 
or generally how important that at_console block is for them.

Again, thanks :)


On 02/20/2016 03:38 AM, Axel Beckert wrote:
> Hi,
>
> thanks toogley for trying to tackle this issue.
>
> Paul Wise wrote:
> > On Sat, Feb 20, 2016 at 3:28 AM, toogley wrote:
> > > what do you think about that? Am i missing sth?
> >
> > I would go with 1) or 3) add support for systemd-logind and whatever
> > other options there are for people who don't like systemd (ConsoleKit2
> > etc) and send that to upstream.
>
> Indeed, thanks Paul for that comment.
>
> wicd seems the most popular alternative to NetworkManager for those
> who dislike NetworkManager's hard dependency on libpam-systemd and
> hence systemd.
>
> So to add an exclusive hard dependency on anything systemd-ish would
> probably annoy a not so small part of wicd's user base in Debian and
> should be avoided.
>
> Making use of systemd features if systemd is installed, is though
> welcome. This means that according configuration files should be
> shipped, but wicd should not solely rely on them -- as it seems to
> have happened with consolekit in the past.
>
> 		Regards, Axel