3 ms·
Assuming binary-only distribution, you already have this problem for a multitude of distros. If you're employing such a proprietary model, you'll obviously have
by vezzy-fnord 11y ago
Assuming binary-only distribution, you already have this problem for a multitude of distros. If you're employing such a proprietary model, you'll obviously have problems you'll need to overcome.
Assuming source distribution, I do not see any special effort required.
This is a protectionist, anti-choice argument.
- creshal 11y ago> Assuming source distribution, I do not see any special effort required. No special effort to support Mir/Unity/upstart? Other Ubuntu-only APIs, standards, UX, Kernel/Library versions not employed by other distributions, …? (Upstart was killed when even Canonical realized it was impossible to demand of everyone else to support their special snowflake init system.)
- vezzy-fnord 11y agoFor the record, most projects do not supply configurations for every possible userspace plumbing, but either none or only select ones. Upstart jobs would be written by the distribution maintainer or user. Mir hasn't even rolled out yet, and IIRC it has X11 compatibility anyway. Why would you need special effort to support Unity other than a .desktop file, which is interchangeable with GNOME (Unity reuses GNOME under the hood)? Kernel and libraries do not require special effort at all to support when distributing source. It's also funny how people routinely bitch about Upstart when it predated systemd.