On Sun, Nov 3, 2019 at 16:42, Michal Suchánek <msuchanek@suse.de> wrote:
On Sat, Nov 02, 2019 at 10:41:37AM +1030, Simon Lees wrote:
Am Freitag, 1. November 2019, 01:12:55 CET schrieb Simon Lees:
On 11/1/19 12:11 AM, Hans-Peter Jansen wrote:
An external management of package grouping is doomed to die, as
On 11/1/19 11:18 PM, Hans-Peter Jansen wrote: the amount
of work will surpass it's usefulness.
Many consider that the state the internal management of groups would equally indicate that it had failed.
I'm inclined to disagree.
Well, in fact, if you reread the answers to Ludwig's proposal, you find mostly refusals or warnings to take that route.
Between them there are suggestions from people who are either heavily involved or that have been heavily involved in release management agreeing that it would be a better solution for them to be external, including reasons that it would be technically Superior such as translations.
Well, managing groups outside of specs, I can see a slight improvement in translation handling, but the comes with an even higher prize of disjoint group management.
What technical reasons hinders the translation of a collection of tags exactly?
Generally translations are stored in the binary alongside the original strings or in a separate file that ships with the binary that it loads and uses rpm doesn't really have support for handling translations in its metadata in any form and if it did our the software our translation team use isn't set up to search across obs to find translation strings in all the spec files. Where as if we do groups externally its easy to intergrate into our existing translation software.
But we can have data on all binaries collected so cnf can do its job.
That's not really needed long term, we can use the createrepo_c's filelist file (which is automatically generated for every obs repository) to see what package has files in /usr/bin or /bin (+sbin). We don't use that anywhere really, if we did, we could use packagekit's cnf instead of scout, and search any and all arbitrary files within remote and local packages. Currently the only files we can search are capabilities and locally installed rpms, which is very limiting. LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org