Mailinglist Archive: zypp-devel (78 mails)
| < Previous | Next > |
[zypp-devel] libzypp for openSUSE 11.0
- From: Stanislav Visnovsky <visnov@xxxxxxx>
- Date: Fri, 2 Nov 2007 13:02:07 +0100
- Message-id: <200711021302.07679.visnov@xxxxxxx>
Hi!
I'd like to start a discussion how to move forward with libzypp for 11.0.
Here is the list of possible improvements I'm aware of:
- User interface
Work on design, usability of YaST the package management frontends.
- Application layer
Applications using libzypp duplicate a lot of code which should be
refactored into an application layer on top of zypp.
- PackageKit
PackageKit, building upon PolicyKit, allows to assign specific
(administrative) rights in regards to software management.
- New SAT solver
A new approach to dependency solving seems to overcome the
limitations of the current solver, while
implementing most of the requested features.
(see http://idea.opensuse.org/content/ideas/fast-installation-tool)
- Build service integration
Client-side software management should be integrated with build
service functionality in order to support online search and
on-demand information like ratings and screenshots.
- Redesign of the caches
This comprises the SOLV files and way to store the additional data
to be retrieved on-demand, etc.
- zypper improvements
There is quite some work left to improve zypper, fix the bugs and fill the
gaps.
- callbacks cleanup
The annoying YaST popups are a direct consequence of the complicated
callback system of libzypp. A redesign and cleanup of the callbacks should
give much better user experience, like
- switch to use librpm directly for installing packages
So far, libzypp calls rpm for every installation of a package, instead of
going directly to librpm
- commit part refactoring
This is mostly about providing parallel download of packages and also
installing more than one package per transaction. Another related feature is
to keep the downloaded packages available on the disk.
- locking storing and application API
10.3 allows user to configure locking using /etc/zypp/locks file, however,
there is no GUI to do this.
I believe there is more... I've tried to concentrate on larger blocks, not
individual features. Anyway, feel free to add more.
So, comments on the list above? any preferences? Any technical issues why the
particular part is not feasible, or not feasible for 11.0?
Stano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
I'd like to start a discussion how to move forward with libzypp for 11.0.
Here is the list of possible improvements I'm aware of:
- User interface
Work on design, usability of YaST the package management frontends.
- Application layer
Applications using libzypp duplicate a lot of code which should be
refactored into an application layer on top of zypp.
- PackageKit
PackageKit, building upon PolicyKit, allows to assign specific
(administrative) rights in regards to software management.
- New SAT solver
A new approach to dependency solving seems to overcome the
limitations of the current solver, while
implementing most of the requested features.
(see http://idea.opensuse.org/content/ideas/fast-installation-tool)
- Build service integration
Client-side software management should be integrated with build
service functionality in order to support online search and
on-demand information like ratings and screenshots.
- Redesign of the caches
This comprises the SOLV files and way to store the additional data
to be retrieved on-demand, etc.
- zypper improvements
There is quite some work left to improve zypper, fix the bugs and fill the
gaps.
- callbacks cleanup
The annoying YaST popups are a direct consequence of the complicated
callback system of libzypp. A redesign and cleanup of the callbacks should
give much better user experience, like
- switch to use librpm directly for installing packages
So far, libzypp calls rpm for every installation of a package, instead of
going directly to librpm
- commit part refactoring
This is mostly about providing parallel download of packages and also
installing more than one package per transaction. Another related feature is
to keep the downloaded packages available on the disk.
- locking storing and application API
10.3 allows user to configure locking using /etc/zypp/locks file, however,
there is no GUI to do this.
I believe there is more... I've tried to concentrate on larger blocks, not
individual features. Anyway, feel free to add more.
So, comments on the list above? any preferences? Any technical issues why the
particular part is not feasible, or not feasible for 11.0?
Stano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |