Re:Limiting the power of package installation in Debian
by dTal on Friday November 16, 2018 @04:22PM
(#18472075)
You're just saying, "I can constrain whatever I want!".
Which is fine and all, but don't expect users to flock to your distribution that doesn't support $SOFTWARE because you decided they do things wrong.
Re:Limiting the power of package installation in Debian
by Macha on Friday November 16, 2018 @01:01PM
(#18470515)
And JSON-merging and YAML-merging and TOML-merging and .bashrc merging and .properties merging and ...
Re:Limiting the power of package installation in Debian
by geocar on Friday November 16, 2018 @01:36PM
(#18470826)
... and hopefully programmers realise that building all those things and shipping them is harder than just supporting a directory with the plugins in it. Or maybe even just punt with a wrapper that does it at startup.
Honestly: the defence of shit software and user-hostile developers never ceases to amaze me.
You can, if the community wants to go in that direction.
Ideally the software which loads "plugins.xml" is updated to support a conf.d-like directory full of "plugin-pkg1.xml" through "plugin-pkgN.xml", each owned by separate packages. Many OSS projects have done this.
If that's not possible (closed-source, too much work, whatever) then it seems simple enough to build a separate XML-merging tool that the package manager invokes which combines the separate XML files during package installation.