November 2007 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Fwd: automatic removal of unused packages when removing a package
by Jan Kupec 09 Nov '07

09 Nov '07

(initial message, several replies will be forwarded shortly) Hi, We've received several requests to provide a feature to automatically remove unused packages resulting from removing a package (or more packages). For example: i want to install 'glest': glest needs glest-data so both get installed. Then i get bored with glest and want to remove it, but currently using 'zypper remove glest' will remove only 'glest', glest-data stays needlessly installed. What i want to achieve is something like: $ zypper remove --auto-remove-whathever glest .... The following packages are going to be REMOVED: glest-data glest (maybe with an additional section in the summary like this: The following package is unused and will be removed: glest-data ) It is perfectly reasonable to be able to do this, i just wanted to ask if there already is support for this in the current solver, or it needs to be implemented. BTW: if this is not in current solver yet, i don't known whether this should be implemented in the SAT solver or still in the current solver. Cheers, Jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 5

[zypp-devel] Re: [zypp-commit] r7763 - /trunk/sat-solver/tools/attr_store.c
by Michael Andres 09 Nov '07

09 Nov '07

On Fri, Nov 09, kkaempf(a)svn.opensuse.org wrote: > Author: kkaempf > Date: Fri Nov 9 11:27:53 2007 > New Revision: 7763 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=7763&view=rev > Log: > fix the build > > Modified: > trunk/sat-solver/tools/attr_store.c > > Modified: trunk/sat-solver/tools/attr_store.c > URL: http://svn.opensuse.org/viewcvs/zypp/trunk/sat-solver/tools/attr_store.c?re… > ============================================================================== > --- trunk/sat-solver/tools/attr_store.c (original) > +++ trunk/sat-solver/tools/attr_store.c Fri Nov 9 11:27:53 2007 > @@ -697,10 +697,10 @@ > s->stringhashmask = 0; > > fprintf (stderr, "%d\n", old_mem); > - fprintf (stderr, "%d\n", s->entries * sizeof(s->ent2attr[0])); > + fprintf (stderr, "%ld\n", s->entries * sizeof(s->ent2attr[0])); > fprintf (stderr, "%d\n", s->attr_next_free); > - fprintf (stderr, "%d\n", s->abbr_next_free * sizeof(s->abbr[0])); > - fprintf (stderr, "%d\n", s->flat_abbr_next_free * sizeof(s->flat_abbr[0])); > + fprintf (stderr, "%ld\n", s->abbr_next_free * sizeof(s->abbr[0])); > + fprintf (stderr, "%ld\n", s->flat_abbr_next_free * sizeof(s->flat_abbr[0])); > fprintf (stderr, "pages %d\n", s->num_pages); > s->packed = 1; > } /Local/ma/zypp/sat-solver/tools/attr_store.c:700: warning: format '%ld' expects type 'long int', but argument 3 has type 'unsigned int' /Local/ma/zypp/sat-solver/tools/attr_store.c:702: warning: format '%ld' expects type 'long int', but argument 3 has type 'unsigned int' /Local/ma/zypp/sat-solver/tools/attr_store.c:703: warning: format '%ld' expects type 'long int', but argument 3 has type 'unsigned int' -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- 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] How do I select specific packages in zypper/yast2?
by Aniruddha 05 Nov '07

05 Nov '07

With smart I can use a specific version like this: smart install kernel-source-2.6.22.5-31. How do I achieve the same with zypper/yast2? I also noticed that smart replaces the old package with the new one while this isn't really necessary. How do I prevent this in zypper/yast2? # smart install kernel-source-2.6.22.5-31 Loading cache... Updating cache... ############################################################################ [100%] Computing transaction... Downgrading packages (1): kernel-source-2.6.22.5-31@x86_64 49.3MB of package files are needed. 14.9kB will be freed. Confirm changes? (Y/n): -- Regards, Aniruddha Please adhere to the OpenSUSE_mailing_list_netiquette http://en.opensuse.org/OpenSUSE_mailing_list_netiquette -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 6

[zypp-devel] Re: [zypp-commit] r7719 - /trunk/sat-solver/src/DISCUSS
by Duncan Mac-Vicar Prett 01 Nov '07

01 Nov '07

> Solver algorithms: > ------------------ > > - the solver allows arch changes from/to noarch without complaining. > good or bad? good question. noarch is supposed to work, but I am not sure if this usecase really happens often. I can imagine a java package getting rid of some native extension, in this case the noarch package wll be the enhanced one by the package maintainer. > - vendow changes are allowed from unknown to known. libzypp doesn't > allow that. Feature? There are not known vendors, there are vendor changes, and current libzypp behaviour is not select a different vendor in a upgrade as candidate, unless it s a explicit user transaction. > - arch changes are only considered if the name stays the same, so > a rename can install a different architecture. bug? > - same with vendor. bug :-) > - should prune_best_version_arch consider the arch or the vendor this > is about an installed package? what does it do? > - we disable conflicting rules when searching for a suggestion, should > we first extend them with arch changes/vendor changes/downgrades? > In what order? I dont understand. > - distupdate sets 'allowuninstall'. Should it only allow uninstall > for packages that do not have an update in the repositories? No idea. > - splitprovides don't work at all. > > - repo priorities should influence the order in which package rules > are fulfilled. why? I think repo priorities are no more than part of the policy to select a candidate. I think in tis aspect the solver should implement something flexible, like a callback passing candidates and context and returning the selected one, or giving each of them scores. > - weak systemrules should be created for all installed packages, so > that they are available when the erase rule is disabled if a > suggestion is calculated. what are weak system rules? a installed rpm recommends? > - should we implement weak systemrules as weak rules? ?? > - prune_best_version_arch has a n^2 loop when looking at obsoletes. > Should we create an obsoletes index to speed that up? ZYpp right now has indexes for all kind of requries, and that is why it needs all dependencies in the pool before solving, to build those. > Code cleanup: > ------------- > - move whatprovides/whatprovidesdata from pool to solver? > good: can implement installed(), though I don't know if we need I wanted to implement each_installed() in the solver (ruby) > bad: need to allocate solver if we just want to look up a provides. > can't re-use whatprovides for multiple solver runs with different > solvers. it can be in the pool and wrapped in the solver. The solver has access to the pool but not viceversa > - implement unified idarray in pool, so that repos don't have to > come with their own idarrays? Would need memory for hash, but > unification would be a nice thing. Would also fix solver memory > leak with learned rules. Needs some hard numbers abour memory usage. No idea here. > - make bitmap macros inline functions? it is ok as long as they are well documented and it the right header. > - rename ID Macros to ID_, e.g. ARCH_NOARCH to ID_ARCH_NOARCH? Everything that makes things explicit and intutive-> principe of least surprise -> is welcome. > - support different streams than FILE in repo_ functions? Is it > enough that glibc supports FILE overloading, see the undocumented > fopencookie()? For ruby bindings it was no problem to work with FILE. Still, I am thinking of the use case of an application server, where you want to load the repos once in memory and share them across requests. It is a valid use case (I already saw it), but I have no idea how to support this. -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg 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

4 4