Hello, On 01/09/14 11:42, Mike Gabriel wrote: > as I am currently working on a thinclient environment for X2Go which > needs such an alt-init approach beyond wheezy, I will be happy to > help-out with sponsoring and testing. Great! I was quite sure there will be users who need such a setup for backward-compatibility. d-i support for Blends sounds like a really easy way that doesn't require custom install discs. (If other people have good uses cases for this, please mention them). The systemd-must-die 'anti-package' tried to do this another way and was rejected. I hope a Blend would be a more constructive approach. I'm thinking sysvinit would be the easiest 'flavour' to implement for jessie, but others are possible, probably only using legacy Sys-V init compatibility rather than native service files, for now. sysvinit scripts will still be in use on the kfreebsd and hurd ports for jessie, so most packages will still ship them even if they have systemd units also. We have a tech-ctte resolution in our favour, that reasonable changes should be accepted into packages to make sure alternative init systems work. I don't currently expect GNOME to work properly without systemd, I'd prefer to focus on other desktops instead, but if GNOME's basic functionality still works that would be nice. (I wonder if the bugreport template could mention if a non-default init system is used). I'm going to have a read over ITP procedure, mentors.d.n and Blends documentation and then I will get back to you. Thanks! Regards, -- Steven Chamberlain steven@pyro.eu.org
Attachment:
signature.asc
Description: OpenPGP digital signature