[zypp-devel] some features that may simplify client code
I have been reading the PackageKit backend code and with my knowledge of zypper and YaST code, I thought some cleanups and features that may be useful to remove code duplication. I accept feedback on how they could be approached: - A more transparent/direct way to add a plain rpm file to be installed Affected: zypper, PK Right now both create temporary plaindir repositories, and then remove them after installing the packages, with all the required error handling - A better updates Pool "View" Affected: PK PK does some acrobatics getting all required patches, then all package updates, and then removing the package updates that are included in the required patches. May be this could be made a kind of updates Pool view that automatically iterates over patches, packages not included in the patches, and that can easily turn patches or shypackages on/off On the other hand the following features would increase usability (as discussed in the conference): - gpg key trust transitivity... however a whole review of the keyring code would be good -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Dne 4.11.2010 15:53, Duncan Mac-Vicar P. napsal(a):
- A more transparent/direct way to add a plain rpm file to be installed Affected: zypper, PK Right now both create temporary plaindir repositories, and then remove them after installing the packages, with all the required error handling
This approach is also a used in YaST, implemented in YCP (in sw_single.ycp). But it should be easy to move the functionality to pkg-bndings and use libzypp functionality.
- A better updates Pool "View" Affected: PK
PK does some acrobatics getting all required patches, then all package updates, and then removing the package updates that are included in the required patches. May be this could be made a kind of updates Pool view that automatically iterates over patches, packages not included in the patches, and that can easily turn patches or shypackages on/off
Pkg bindings also have some code for iterating over patches: for preselecting or counting available/applicable patches. I don't know how much it is related to the pk-zypp backend... -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (2)
-
Duncan Mac-Vicar P.
-
Ladislav Slezak