Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Wednesday November 19 2014, @11:25AM   Printer-friendly
from the I-hope-we-don't-regret-this dept.

Ian Jackson's general resolution to prevent init system coupling has failed to pass, the majority vote deciding that the resolution is unnecessary. This means that not only will Debian's default init be systemd, but packages will not be required to support other init systems. Presumably, this means that using other init systems on Debian (without using systemd as a base) will not be possible without major workarounds, or possibly at all. It also leaves the future of Debian projects such as kFreeBSD unclear, as systemd is linux specific.

The vote results can be found here

The winners are:

Option 4 "General Resolution is not required"

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by fnj on Wednesday November 19 2014, @05:37PM

    by fnj (1654) on Wednesday November 19 2014, @05:37PM (#117755)

    I'm not entirely sure how to keep track of binary packages and ports that have been manually compiled

    Yes, this is a weakness. I had to compile postfix from ports because the binary package was compiled with stupid options. Then "pkg upgrade" will try to stomp on it if a newer binary package appears. What I did discover is that you can "pkg lock postfix" to prevent this. So now you can safely run "pkg upgrade" again. Until you "pkg unlock postfix", it will bypass any newer postfix packages.

    Hope this helps.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by cockroach on Wednesday November 19 2014, @05:43PM

    by cockroach (2266) on Wednesday November 19 2014, @05:43PM (#117758)

    Hope this helps.

    It does indeed, thank you!