On Wed, Aug 12, 2020 at 11:13, Neal Gompa <ngompa13@gmail.com> wrote:
On Wed, Aug 12, 2020 at 10:39 AM Lubos Kocman <lubos.kocman@suse.com> wrote:
No support for products
WTF are these?
They are kinda pointless nowadays, aren't they. We could have a product-like provide that does pretty much the same thing. Not to mention appstream operating-system metadata provides pretty much all that product does (and it's an existing standard!), we would just have to ship it
No support for patterns
These are just metapackages, but it wouldn't be hard to add a subcommand similar to the "group" one to manage these.
Not to mention, they already work with dnf as they are, since they are just rpm packages with placeholder content that depend, recommend and suggest some other packages.
No support for services
Wut?
It's one of those things where I really don't understand why it would ever be useful https://doc.opensuse.org/projects/libzypp/HEAD/zypp-services.html It also could really be a dnf plugin
No support for product licenses
Wut? Is this the SUSE metadata extension for packages to have EULAs? Or something else?
Always makes me wonder why stuff like this doesn't land in RPM first
I don't see how YaST can work with libdnf
This makes no sense to me. What do you mean by that?
I don't see how YaST couldn't work with libdnf. On the language side, considering most of YaST stuff dealing with libzypp is written in C++, that's doable. There are some parts in ruby that deal with zypper invoked in the middle of code, we could have libdnf bindings for ruby exposed so those parts can use an actual api. Maybe it's just lazyness, that I can understand. The holdup on getting dnf used here seems to be political more than technical, I don't think I wanna know how this discussion looks internally ;) 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