On Fri, Feb 21, 2020 at 8:43 AM Stefan Seyfried
Am 21.02.20 um 02:21 schrieb Neal Gompa:
No, this whole thread suggests that massive co-ownership like this is a bad idea. It's too easy to trigger conflicts everywhere in ways that are hard to diagnose. This is a major aspect of openSUSE packaging that I *really* don't like compared to Fedora, Mageia/Mandriva, and others.
How do they handle the issue? Does their filesystem package contain more directories? But then, /usr/share/metainfo (which was the directory in question here) does belong to "filesystem" already, at least in 15.1... so I don't really understand where the error is coming from at all...
Well, usually there's one "golden owner" until it makes it into "filesystem", (for example, appstream had a -filesystem package). Depending on the type of directory thing, the path may move to filesystem or stay as a filesystem subpackage. The latter case is how httpd and nginx filesystem paths are maintained today. There's a fair number of <package>-filesystem packages in Fedora for this purpose, and this strategy allows for loosely coupled paths to be still owned by a single package, making it *much* easier to figure out what directories actually belong to and are for.
If it is because of building for older distributions, then probably the best solution is to just remove the metainfo directory and content from the package... ;-)
Nah, it's just because the openSUSE policy is lazy in this regard and doesn't mandate figuring out a "golden owner" for a path. -- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org