Mailinglist Archive: zypp-devel (78 mails)
| < Previous | Next > |
Re: [zypp-devel] libzypp for openSUSE 11.0
- From: "Benji Weber" <benji.weber@xxxxxxxxx>
- Date: Fri, 2 Nov 2007 14:23:03 +0000
- Message-id: <d6b310ce0711020723o799d6340x58a857dd37dda70e@xxxxxxxxxxxxxx>
On 02/11/2007, Stanislav Visnovsky <visnov@xxxxxxx> wrote:
Great
Sorely needed, also it would make sense to try to make the KDE & GNOME
package selectors as consistent as possible for usability &
documentation & support reasons.
Packagekit looks quite nice, one potential issue I've seen is that
they don't have any way to add repositories as on RH/Fedora they seem
to use packages containing the .repo files and install those packages
to add repositories. (Please correct me if this is completely wrong)
Not sure if the server side for this is likely to be ready for 11.0
looking at build service roadmap. There was also some discussion as to
whether it should be added into the buildservice or a separate
component so that it could be community hosted with fewer legal issues
& include non-buildservice software.
I had a look at this earlier this week, see
http://bw.uwcs.co.uk/new_callbacks.ogg
I would like to propose:
- Diffed metadata
While it will make virtually no difference for factory where checksums
of nearly every package changes almost every sync. It would make a
large difference for Packman, KDE:KDE3, GNOME:Community,Update
Repository etc etc. Where often there are one or two packages
appended. Probably most users have the packman repository and it is
updated almost every hour - a 5mb download to retrieve maybe 100kb of
new data. Supporting this would be even more visible than speeding up
repository cache reading/solving imo.
There was another feature I thought was very important, but I've
completely forgotten it, will post it when I remember.
--
Benjamin Weber
--
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.
Great
- User interface
Work on design, usability of YaST the package management frontends.
Sorely needed, also it would make sense to try to make the KDE & GNOME
package selectors as consistent as possible for usability &
documentation & support reasons.
- PackageKit
PackageKit, building upon PolicyKit, allows to assign specific
(administrative) rights in regards to software management.
Packagekit looks quite nice, one potential issue I've seen is that
they don't have any way to add repositories as on RH/Fedora they seem
to use packages containing the .repo files and install those packages
to add repositories. (Please correct me if this is completely wrong)
- 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.
Not sure if the server side for this is likely to be ready for 11.0
looking at build service roadmap. There was also some discussion as to
whether it should be added into the buildservice or a separate
component so that it could be community hosted with fewer legal issues
& include non-buildservice software.
- 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
I had a look at this earlier this week, see
http://bw.uwcs.co.uk/new_callbacks.ogg
I believe there is more... I've tried to concentrate on larger blocks, not
individual features. Anyway, feel free to add more.
I would like to propose:
- Diffed metadata
While it will make virtually no difference for factory where checksums
of nearly every package changes almost every sync. It would make a
large difference for Packman, KDE:KDE3, GNOME:Community,Update
Repository etc etc. Where often there are one or two packages
appended. Probably most users have the packman repository and it is
updated almost every hour - a 5mb download to retrieve maybe 100kb of
new data. Supporting this would be even more visible than speeding up
repository cache reading/solving imo.
There was another feature I thought was very important, but I've
completely forgotten it, will post it when I remember.
--
Benjamin Weber
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |