3 ms·
Because the scope of 'certain reindexing actions' is potentially unbounded. Suppose you have a large piece of software that uses plugins, which it finds by read
by dTal 8y ago
Because the scope of 'certain reindexing actions' is potentially unbounded. Suppose you have a large piece of software that uses plugins, which it finds by reading a 'plugins.xml' file. Now, when you install a plugin from the package manager, you need to modify 'plugins.xml' in some arbitrary fashion. You simply cannot constrain the entire software world to operate in a file-oriented, declarative manner.
- jjnoakes 8y ago> You simply cannot constrain the entire software world to operate in a file-oriented, declarative manner. 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.
- Macha 8y agoAnd JSON-merging and YAML-merging and TOML-merging and .bashrc merging and .properties merging and ...
- geocar 8y ago... 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.
- dTal 8y agoYou'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.