On Mon, 2019-10-28 at 12:20 +0100, Hans-Peter Jansen wrote:
Am Montag, 21. Oktober 2019, 10:52:48 CET schrieb Simon Lees:
If Yast is never going to support groups again then personally
I'm missing yet another reason for using yast sw_single.
Let's spin it the other way around:
Given, we have established an improved grouping classification for the available packages, more people *will* find a grouping view in yast useful.
I think you should consider a hard fact of life - it doesn't matter what a small number of vocal users and/or contributors decide in their own ecochamber, if the actual developers of a tool do not agree, they are under no obligation to impliment any tooling to support any such classification. The YaST team made a concious decision to remove code they knew they no longer wished to support that utilised metadata which a public discussion had (at the time at least) clearly shown to be unnecessary to the Project. Now, the YaST team are quite within their rights to set the barrier as high as they like before they will be convinced to add any new Group- handling functionality. And without tooling making such of such metadata, I think it's an unreasnoble burden on all of our packagers to be expected to follow it in any sort of mandatory manner. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org