December 2007 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] out of office
by coolo＠suse.de 28 Dec '07

28 Dec '07

I will be back on January 7th. Have some fun anyway, your mail about "[CruiseControl] zypp-trunk build 8156 failed" will be answered then. Greetings, Stephan -- 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] Re: [zypp-commit] r8131 - in /trunk/sat-solver/bindings: ruby/CMakeLists.txt ruby/ruby.i ruby/satsolver.rb ruby/tests/ ruby/tests/loading.rb ruby/tests/pool.rb ruby/tests/repo.rb satsolver.i
by Duncan Mac-Vicar P. 21 Dec '07

21 Dec '07

On Thursday 20 December 2007 11:19:47 pm kkaempf(a)svn.opensuse.org wrote: > Author: kkaempf > Date: Thu Dec 20 23:19:47 2007 > New Revision: 8131 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=8131&view=rev > Log: > put some love into the bindings great! > - dont generate everything from .h file, but selectively Uhm, does that mean we will have to sync by hand? > whats actually needed what is excluded now? > - add test cases for Ruby bindings nice :-) Why did you change cxx to .c when the output is actually a C++ source (the OO layer is inlined) Cheers Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 5

[zypp-devel] Re: [zypp-commit] r8127 - in /branches/tmp/ma/jump_sat/libzypp/zypp: ./ base/ parser/susetags/ pool/ sat/ sat/detail/
by Michael Matz 19 Dec '07

19 Dec '07

Hi, On Tue, 18 Dec 2007, mlandres(a)svn.opensuse.org wrote: > Author: mlandres > Date: Tue Dec 18 21:49:35 2007 > New Revision: 8127 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=8127&view=rev > Log: > - Changed ResKind implementation to use IdStr. > - split Solvable ident into kind/name > - map src/nosrc Solvables to kind(SrcPackage) and arch(noarch) I think it would be better if either libzypp would do away with the Solvable kind altogether, or implement this so that it doesn't take up any space in the libzypp wrapper of the sat Solvable structure. I can't really see how fantastically usefull the kind is to deserve it having an own member. The only uses I can imagine are of the type "give me only Patches" or "don't search Patterns" and the like. The old solver also uses them in Dependencies, but let's ignore that, as it's going away. So, in all cases you already have a Solvable, hence the complete SAT Name, which includes the "type". I think it would be better to compute the kind from that whenever it's necessary, instead of storing it. It can be done quite fast when we assume that ':' doesn't occur normally in a name (we can assume that): int solv2kind (Solvable *s) { if (s->arch == ARCH_SRC || s->arch == ARCH_NOSRC) return KIND_SOURCEPACK; const char *name = id2str(s->name); // make sure we have four characters if (!(name[0] && name[1] && name[2] && name[3])) return KIND_PACKAGE; int len = 0; int kind = 0; switch (name[3]) { // we look at the fourth character --------v case 'm': len = 4; kind = KIND_ATOM; break; // atom case 'g': len = 8; kind = KIND_LANGUAGE; break; // language case 's': len = 7; kind = KIND_MESSAGE; break; // message case 'c': len = 5; kind = KIND_PATCH; break; // patch case 't': len = 7; kind = KIND_PATTERN; break; // pattern case 'd': len = 7; kind = KIND_PRODUCT; break; // product case 'e': len = 9; kind = KIND_SELECTION; break; // selection case 'i': len = 6; kind = KIND_SCRIPT; break; // script default: return KIND_PACKAGE; } int i; // make sure string doesn't end before the position of the ':' for (i = 4; i < len && name[i]; i++) ; if (i == len && name[i] == ':') return kind; return KIND_PACKAGE; } This needs to touch just one cache line of something which most probably is in cache already (the name) and hence is only slower by a couple of cycles compared to directly having the kind stored away. But it saves half the size of Solvables. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 5

[zypp-devel] Question about searching for packages
by Wade Berrier 19 Dec '07

19 Dec '07

Hi, Is there a way to make package searches from yast or zypper search the summary and description tags? Example, we have a package called IPCE. It's IronPython with some addons. So, it'd be nice to be able to search for ironpython and have IPCE show up. Console output: zypper shell zypper> search ironpython * Reading installed packages [100%] No resolvables found. zypper> search ipce S | Repository | Type | Name | Version | Arch --+------------+---------+------+---------+------- | opensuse | package | IPCE | r6-15 | noarch zypper> Any ideas or suggestions of how to make this work would be great. Thanks, Wade -- 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] Honoured dependency types
by Cristian Rodríguez 17 Dec '07

17 Dec '07

Hi: Are all of the Dependency types listed here: http://en.opensuse.org/Software_Management/Dependencies Honoured by zypp ? especifically the "weak, conditional and reverse dependencies" ? if so, what are the rules of the game? f.e Reccommends is triggered on patches too, which is a quite unexpected behaviuor, a "patch" in my understanding corrects an already installed package and only pull new ones when they are stricly "Required".. ;-) Cheers... -- "The only thing that interferes with my learning is my education." - Albert Einstein Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 3

[zypp-devel] How to get a packages' depends and requires from libzypp
by Boyd Timothy 14 Dec '07

14 Dec '07

I'm trying to implement: 1) GetDepends (http://www.packagekit.org/pk-reference.html#api-get-depends) - GetDepends should return packages that this package depends on. 2) GetRequires (http://www.packagekit.org/pk-reference.html#api-get-requires) - GetRequires should return packages that depend on this package. This is useful to know, as if package_id is being removed, we can warn the user what else would be removed. I can't figure out what to call. I've got a zypp::Resolvable::constPtr and I notice there's a ->deps(). I've cycled through that, but end up getting a long list of both packages and libraries. Does anyone have some sample C++ code that I could look at to see how I might implement these methods? Thanks, Boyd -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

9 21

[zypp-devel] Getting a refresh to work
by Boyd Timothy 14 Dec '07

14 Dec '07

PackageKit defines two types of cache refreshes. One of them forces a refresh and the other doesn't. If you take a look at our code here: http://pastebin.ca/812559 ...are we doing anything wrong. A standard refresh (one without a force) seems to work okay. When I do a force refresh, I get an error, "Valid metadata not found at specified URL(s)". Suggestions? Thanks, Boyd -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1

[zypp-devel] Question / remark about zypper solving dependencies
by Dominique Leuenberger 13 Dec '07

13 Dec '07

Hello, I have an interesting observation: Several Repos activated. Let's call them Repo1 and Repo2. Repo1 provides: pkgA-0.1-1 Repo2 provides pkgA-0.2-1 libpkgA0-0.2-1 (libpkgA was split out from pkgA with the new version, according to the SO-Policy) pkgB-1.0-1 pkgB requires a Shared library, only by the symbol (so no forced Requires:). The symbol is provided by libpgkA0-0.2-1 and also by pkgA-0.1-1. So far, I think every thing is clear (hopefully also clearly illustrated). Now the thing (using zypper): zypper shell zypper> in pkgA it install pkgA-0.2-1 and also libpkgA0-0.2-1 (because one of the binaries within pkgA requires the lib) so: this is exactly as I would say it should be. pkgA-0.2 being newer than 0.1 get's precedence and is thus selected. Now let's 'uninstall' them from the system (no matter how, zypper rpm... just get back to clean state ;) ) zypper shell zypper> in pkgB in this case, zypper resolves the dependencies and offers to install pkgA-0.1-1 Why doesn't it suggest now also to install pkgA-0.2-1 together with libpkgA0-0.2-1? Wouldn't that case be the logical one? a consecutive lu -t package shows that pkgA is 'upgradeable' and a in pkgA pulls it, together with libpkgA0 in... Interesting case for any of the solver hackers around? Or do you think such a case should be 'caught' by the RPM builder, with a Obsoletes: pkgA < 0.2 in the libpkgA0 package? (would be possible I guess, but having a newer pkgA makes it look a bit weird) Dominique -- Sorry for the annoying disclaimer coming now. TMF is a global management and accounting outsourcing firm with 77 offices in 60 countries and over 2,500 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 3

[zypp-devel] make_wrapper for CMake vs. Autotools Projects
by Stefan Hundhammer 12 Dec '07

12 Dec '07

[Re-posted from yast-devel(a)opensuse.org for those of you who are not subscribed there] New script: http://svn.opensuse.org/svn/yast/trunk/devtools/yast2/make_wrapper (or: svn up devtools) This is a script you can use to make life more convenient when working with both CMake and autotools based projects: CMake is intended for building out of the source tree. Autotools (and pure "make") build in the same tree where the source files are. If you have both kinds of projects, you always have to keep in mind where to "cd" to (or to what shell window to go) to invoke "make". And for CMake out-of-source-tree building it's really hard to invoke "make" directly from the editor of your choice so it can immediately load the source file where the compiler reported an error and fix it. Coolo suggested to use the "makeobj" script from the KDE 4 SDK, but not only does this require the user to set environment variables where the build tree is, it also does not seem to work well in mixed CMake / Autotools environments. So I wrote this "make_wrapper" script that checks the current directory for a file "Makefile" and call "make" there directly if there is one. If there is none, it checks ../build/Makefile, then ../../build/Makefile etc. All you have to do is stick to that convention to name the CMake out-of-source-tree build directory "build" (configurable in the script of course) and simply call "make_wrapper" rather than "make". The toplevel Makefile.cvs in libzypp and yast2-qt4 support that anyway: They create a "build" directory and invoke "cmake" there. Emacs users might want to set their "compile-command" variable in ~/.emacs : (setq compile-command "make_wrapper -k && sudo make_wrapper install") or, when using "icecream" distributed compilation: (setq compile-command "make_wrapper -k -j20 && sudo make_wrapper install") CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- 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] Fwd: [packagekit] Questions about Get Depends and Get Requires
by Boyd Timothy 11 Dec '07

11 Dec '07

FYI: More information from the PackageKit developer about the GetDepends() and GetRequires() calls... ---------- Forwarded message ---------- From: Richard Hughes <hughsient(a)gmail.com> Date: Dec 11, 2007 1:00 AM Subject: Re: [packagekit] Questions about Get Depends and Get Requires To: PackageKit users and developers list <packagekit(a)lists.freedesktop.org> On Thu, 2007-12-06 at 08:02 -0700, Boyd Timothy wrote: > 1) I noticed that libzypp doesn't just return package dependencies, > but also single libraries and files. Some of these libraries can be > provided by multiple packages. Do any other PackageKit backends have > to deal with that? ...and if so, what's the recommended thing to do? > Just return pacakges? Yes, just packages. The other stuff isn't important to PackageKit. > 2) How does dependency resolution work in the GUI? For testing > purposes, I wrote a fake Get Requires which returned three fake > packages. I expected pk-application to prompt me about the other > packages when I installed "lynx", but it didn't. Sure, it just installed lynx and whatever else it needed. I don't see the need to ask the user to install openoffice-fonts, openoffice-clipart, openoffice-thesarus etc just because they want openoffice installed. > 3) When GetDepends and GetRequires are called, they should return all > packages regardless of their installed state, right? Yes. Cheers, Richard. _______________________________________________ PackageKit mailing list PackageKit(a)lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/packagekit -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0