We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello YaST team, this one is one of two requests split from https://code.opensuse.org/leap/features/issue/1
The direction that SUSE seemed to agree upon regarding fate of DNF in ALP (PED-163) is to support the community to swap libdnf and libzypp backends.
@Conan-Kudo mentioned that there are two components that seem to be problematic to swap which is yast* and suseconnect-ng.
We'd like to use this tracker for work related to the exchangeability of libzypp and libdnf backends.
The text was updated successfully, but these errors were encountered:
The end goal is to be able to run yast* on top of system which has dnf instead of zypper.
Sorry, something went wrong.
No branches or pull requests
Hello YaST team, this one is one of two requests split from https://code.opensuse.org/leap/features/issue/1
The direction that SUSE seemed to agree upon regarding fate of DNF in ALP (PED-163) is to support the community to swap libdnf and libzypp backends.
@Conan-Kudo mentioned that there are two components that seem to be problematic to swap which is yast* and suseconnect-ng.
We'd like to use this tracker for work related to the exchangeability of libzypp and libdnf backends.
The text was updated successfully, but these errors were encountered: