Software in the Public Interest, Inc. (SPI), publisher of Debian™ GNU/Linux and Debian™ GNU/kFreeBSD™ has reached an agreement in its longstanding trade dress dispute with the Mozilla Corporation, publisher of the Firefox application suite. Under the agreement, SPI will pay an undisclosed sum to the Mozilla Corp. and periodically turn over marketing data regarding SPI's customers. In exchange, SPI will receive a nonexclusive license to distribute the Firefox suite as part of SPI's Debian™ products.
SPI agreed not to alter the branding of the Firefox suite; not to disable its Pocket integration; not to alter the suite's anti-phishing or search features, which are sponsored by Mozilla Corp. partners; and to discontinue its competing Iceweasel Web suite, which is based on Mozilla Corp. software licensed under a previous accord. The Firefox suite will be provided to SPI's Debian™ customers as an automatic update via the firm's Dpkg℠ service. The updates will go out over the course of the next three months to groups of randomly selected customers, in order to provide what SPI calls "a superior upgrade experience."
(Score: 3, Interesting) by RamiK on Saturday April 02 2016, @06:27PM
systemd wasn't the problem. The problem is Debian's governance and packaging policies. Debian always was extremely biased towards certain people and interests. And the bloodied conflicts stretch all the way back to the Enlightenment WM era when Rasterman got back-stabbed and pushed out. Ubuntu and Mint are recent symptoms of the problem as well. Why did it take a committee to allow a package in? Why only maintainers who know a guy, who vetted a guy, were allowed in? It was a private club of little development, and much bitchiness. It allowed a vocal majority to push out a technical minority then, and it allowed a corporate sponsored mob to push out the old guard now. Not only Debian didn't reflect the development model of projects, it disproportionately represented the developers themselves in favor of package maintainers.
And the proof is in the pudding: People moved on to other distributions that also use systemd while developers even started deploying docker containers. Arch's AUR neutralizes all the political crap so it attracted the first wave to jump ship. But as time went by, real technical package distribution solutions to reproducibility and library conflict in NixOS and GuixSD - that potentially solve the same bullshit politics AUR solved - started creating their own buzz.
If people really feel so strongly about the issue, they should repackage \ extend GuixSD with non-free repositories and an installer or join in on NixOS instead of wasting time on forking Debian. Solve the problems where your efforts would be appropriated by likewise people. Let Debian and the Ubuntu user-base rot under it's corporate overlords.
compiling...
(Score: 2) by maxwell demon on Saturday April 02 2016, @07:24PM
No, it isn't. I just ate the pudding, and couldn't find a proof in it.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by RamiK on Saturday April 02 2016, @10:00PM
Aha! But did you drink the cool aid? :D
But seriously, conventional distributions and systemd go too well together for systemd's faults to ever become an issue worth fighting over. Consider that systemd's overreaching size forces user-land dependencies that non-functional package manager couldn't resolve in the past: Sure, they tried... Debian and Red Hat followed stable releases and backporting patches as best they could. But, eventually herding the linux wildebeests devs was proving too much. Ubuntu and Arch didn't became popular because people were bored, they sacrificed varying degrees of functionality and stability for the sake of newer hardware and software support.
compiling...
(Score: 2) by maxwell demon on Sunday April 03 2016, @07:28AM
Why? Does it generate that whooshing sound?
Hint. [thefreedictionary.com]
The Tao of math: The numbers you can count are not the real numbers.
(Score: 1) by Demose on Saturday April 02 2016, @09:22PM
NixOS' solution looks a lot like Gobo Linux's. It's nice to see new life breathed into old ideas.
(Score: 2) by RamiK on Saturday April 02 2016, @10:32PM
Neither is particularly new. I think both NixOS and Gobo go back about 10 years. I don't think Gobo can pull off the same tricks NixOS can regarding library dependencies. But I wouldn't be able to say for sure.
compiling...