November 2007 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Auto selectables
by Ricardo Cruz 01 Dec '07

01 Dec '07

Hi, Any direct way to know the packages that the resolver has modified? Iterating the pool looking for packages with the Auto status should be good enough for what I want, but just wondering there. Thanks, Ricardo -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 4

[zypp-devel] Where can I find information about the proposed libzypp application API?
by Boyd Timothy 27 Nov '07

27 Nov '07

After talking about the zypp backend for PackageKit, we (Scott, JP and I) were chatting about the Application API we've heard about for libzypp. Could someone let us know: 1. Where can the new API proposal be found? Is it this? http://idea.opensuse.org/content/ideas/better-api-for-applications-using-li… 2. Is anyone currently working on it? 3. When should we expect it to be ready to use? Thanks! Boyd -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 3

Re: [zypp-devel] Can someone do a quick code review for our zypp backend for PackageKit?
by Boyd Timothy 26 Nov '07

26 Nov '07

On Nov 26, 2007 12:10 PM, Timo Hoenig <thoenig(a)suse.de> wrote: > > On Nov 22, 2007 8:18 AM, Duncan Mac-Vicar Prett <dmacvicar(a)suse.de> wrote: > > > > > > > One question guys, > > > > > > is it possible to get the stack running on 10.3? > > > > > > If you have the package in the build service, you could link the dbus factory > > > package to your home project too and build it for 10.3, but I am not sure if > > > the dbus upgrade breaks other stuff? > > > > I'm not sure if that's possible. You'd have to replace dbus, get > > policy kit all working, etc. Perhaps JP has more understanding about > > the surrounding issues? Timo Hoenig may as well. > > Yes, it's possible to use all the new toys on 10.3. However, I'm not > sure if we're building all required packages for 10.3. If there's > something missing I'll can add those packages to my build service repo > and link to the FACTORY sources. So I guess we'd need PolicyKit, PackageKit, DBus, and all their dependencies. Let me know if you need maintainer access to my home:btimothy project on the build service to get this working Timo. Cheers, Boyd -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] RFE: displaying changelog
by Wolfgang Rosenauer 26 Nov '07

26 Nov '07

Hi, I just subscribed here and didn't follow zypp development that near but what I always miss (in YaST and zypper) is the possibility to display the changelog of a package before I install it. rpm-md keeps the changelog in other.xml.gz so it's available at least w/o downloading and parsing RPMs and I'd expect that libzypp should be able to get it "easily". Probably libzypp ignores other.xml currently and that file can be quite big I guess so I think it would be ok to process changelogs only by request which also could take a bit of time but it would be nice to be able to get all relevant information in one place. Wolfgang -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 2

[zypp-devel] Can someone do a quick code review for our zypp backend for PackageKit?
by Boyd Timothy 26 Nov '07

26 Nov '07

As some of you may have seen from my blog post [1], Scott Reeves and I were able to finally get a package to install with the zypp backend for PackageKit! Since we're not the experts with libzypp, we'd love it if some of you could take a look at our code. Are there better ways to do what we're doing (particularly in the backend_install_package_thread function)? Also, we'd like to add notification into the backend so we could notify PackageKit about the progress of installs and such (i.e,. when a package is being downloaded, installed, etc.). How exactly can we do that? Are there callbacks we need to register? Does anyone have any sample code? I've attached our latest file since it appears our changes haven't been pushed out to the anonymous git server yet. Thanks! Boyd [1] http://boyd.musipal.com/2007/11/packagekit-gets-zypp-backend.html

3 7

[zypp-devel] ZYPP future development meeting minutes
by Martin Vidner 21 Nov '07

21 Nov '07

ZYPP future development meeting minutes ======================================= November 19, 2007, Nuernberg Participants: cthiel, coolo, dmacvicar, jkupec, jsrain, kkaempf, ma, mls, mvidner, schubi, visnov Minutes: jsrain, thanks Main areas for development for 11.0 =================================== order votes - sat solver 2 48 - speed-ups - caches refactoring 1 52 - metadata format (download/parsing) 4 43 - commit refactoring 5 33 - switch to librpm - parallel downloads - callback cleanup 7 26 - zypper improvements 6 31 - UI layer 3 45 - PackageKit 9 19 - rpm-only (packages only) 8 27 Explanation: order - the order (final priority for 11.0) votes - group of 11 people, 1 to 5 SLE11 constraint ================ Infrastructure changes can be done only now, not for 11.1 (SLE11) Note: All numbers below mean the final priority People currently working in selected areas ========================================== 1: matz/ma 2: mls/schubi 3: Nuernberg/mvidner 4: benji/matz/dmacvicar 5: 6: jkupec 7: benji/jkupec 8: 9: jpr Inter-area dependencies ======================= 4 Requires 1 3 Requires 2 3 Requires 1 6 Requires 3 5, 6, 7 related to each other (coordination needed) 7, 3 related to each other 8, 3 related to each other Current status ============== 1 - Cache Refactoring - we have the solver format, everything solver needs is in attribute store - storage model needed - parsers which will be used need some discussion - will trigger changes in the resolvable pool - will require most resources, is the most important - needs to be in 11.0 in order to be in SLE11 - ETA: mid January 2 - SAT Solver - solving works, getting suggestions to user works - problems with handling Recommends, Downgrading is a problem, some code needs fixing - integration almost nothing done - if it works, ETA end of November installing with zypper - killing old solver Alpha2 3 - UI layer - High-level spec in the Wiki, low-level WIP - depends on #1 - deadline Beta1 including using the layer 4 to 7: - deadline is Beta1 8, 9: No deadline AIs === AI Duncan: Assign milestones -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] PackageKit gets a Zypp backend
by Duncan Mac-Vicar Prett 21 Nov '07

21 Nov '07

Nice milestone from Boyd! http://boyd.musipal.com/2007/11/packagekit-gets-zypp-backend.html Good job! Thanks JP for pushing this forward in your team ;-) Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] Commits available on irc
by Duncan Mac-Vicar P. 13 Nov '07

13 Nov '07

If you hang out in freenode, the channel #zypp has real time forwarding of commits to the subversion repository. For #yast, the commits go to #yast-commits as they have more traffic than ZYpp repo. The YaST bot includes the ZYpp commits too. Any setting can be changed, so lets see how it works this way! Cheers! Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] libzypp for openSUSE 11.0
by Stanislav Visnovsky 09 Nov '07

09 Nov '07

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(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

10 24

[zypp-devel] Sat-Solver policy engine
by Klaus Kaempf 09 Nov '07

09 Nov '07

Hi, discussions about sat-solver implementation details over the last days showed that a lot of decisions should not (cannot ?) be hardwired. Instead, a policy should be in place to make solver operation configurable. Revision 7734 of sat-solver now contains a generic policy interface (src/policy.h) and a ruby based policy implementation (src/policy-ruby.c). It currently supports a single policy for demonstration purposes. The goal is to make all policies optional and fast for the default case. I'd be interested in defining a concise list of policies. Input welcome ! Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 17