[zypp-devel] zypper exclude-by-arch?
hi, i'm trying to exclude install/update by Arch. package-name wildcards work fine. e.g., adding *32bit* to /etc/zypp/locks works as expected. afaict, there's no manpage mention of arch/locks. trying, *i586* is simply ignored. @irc pointed me to a wiki-page http://en.opensuse.org/Libzypp/Locksfile which is rather a 'challenge' :-/ but, i do see reference to "solvable attributes", solvable attributes this attributes specifies attributes of object. Empty value mean that it restrict global_string on this value. and arch-specific, solvable_sourcearch update_collection_arch iiuc, e.g. to exlcude i586 arch, i add, solvable_sourcearch:i586 update_collection_arch:i586 to locks? can someone please verify/clarify the correct usage for excluding-by-arch, and the difference between "solvable_sourcearch" & "update_collection_arch" thanks! -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
snowcrash+opensuse napsal(a):
hi,
i'm trying to exclude install/update by Arch.
package-name wildcards work fine. e.g., adding
*32bit*
to
/etc/zypp/locks
works as expected.
Hi, if this work as expect then it mean you use opensuse 10.3 which use old lock format which doesn't support arch locking. Wiki page and new manpage locks is for new opensuse 11 and is not yet completed. Josef
afaict, there's no manpage mention of arch/locks.
trying,
*i586*
is simply ignored.
@irc pointed me to a wiki-page
http://en.opensuse.org/Libzypp/Locksfile
which is rather a 'challenge' :-/
but, i do see reference to "solvable attributes",
solvable attributes this attributes specifies attributes of object. Empty value mean that it restrict global_string on this value.
and arch-specific,
solvable_sourcearch update_collection_arch
iiuc, e.g. to exlcude i586 arch, i add,
solvable_sourcearch:i586 update_collection_arch:i586
to locks?
can someone please verify/clarify the correct usage for excluding-by-arch, and the difference between "solvable_sourcearch" & "update_collection_arch"
thanks!
-- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
hi josef,
Hi, if this work as expect then it mean you use opensuse 10.3 which use old lock format which doesn't support arch locking.
well, then i must be wrong re: "as expected", as i'm on opensuse-factory. (hmm ... odd ... must explore)
Wiki page and new manpage locks is for new opensuse 11 and is not yet completed.
yes, i understand the manpage & wikipage are not completed, but ...
can someone please verify/clarify the correct usage for excluding-by-arch, and the difference between "solvable_sourcearch" & "update_collection_arch"
... is it possible to explain nonetheless *how* to properly use these? my ultimate "goal" here is to remove & prevent install of packages="\*32bit" & arch!=x86_64. of course, in rh yum-land, this is done with a simple "exclude='*i386 *i586 *i686'" entry in .conf ... i'm trying to understand howto in opensuse. thanks! -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
snowcrash+opensuse napsal(a):
hi josef,
Hi, if this work as expect then it mean you use opensuse 10.3 which use old lock format which doesn't support arch locking.
well, then i must be wrong re: "as expected", as i'm on opensuse-factory.
(hmm ... odd ... must explore)
Wiki page and new manpage locks is for new opensuse 11 and is not yet completed.
yes, i understand the manpage & wikipage are not completed, but ...
can someone please verify/clarify the correct usage for excluding-by-arch, and the difference between "solvable_sourcearch" & "update_collection_arch"
... is it possible to explain nonetheless *how* to properly use these?
my ultimate "goal" here is to remove & prevent install of packages="\*32bit" & arch!=x86_64. of course, in rh yum-land, this is done with a simple "exclude='*i386 *i586 *i686'" entry in .conf ...
If I good understand you want prevent install any 32bit packages(386,586,686). Then the most efficient way is add to lock file only this line: solvable_name: 32bit this is mean lock ever which have as substring 32bit...so it is same as *32bit* in old format. Of course there is many other ways how to do this. Josef
i'm trying to understand howto in opensuse.
thanks!
-- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
hi josef,
If I good understand you want prevent install any 32bit packages(386,586,686)
yes, that is correct.
solvable_name: 32bit
this is mean lock ever which have as substring 32bit...so it is same as *32bit* in old format. Of course there is many other ways how to do this.
hm. but, "zypper se -s --installed" shows many packages that are installed for BOTH x86_64 (my current arch) *AND i586 that do not have "32bit" in their name ... doesn't "solvable_name" ONLY parse the package_name filed? or does it, also, parse the arch field? thanks! -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
snowcrash+opensuse wrote:
hi josef,
If I good understand you want prevent install any 32bit packages(386,586,686)
yes, that is correct.
solvable_name: 32bit
this is mean lock ever which have as substring 32bit...so it is same as *32bit* in old format. Of course there is many other ways how to do this.
hm. but, "zypper se -s --installed" shows many packages that are installed for BOTH x86_64 (my current arch) *AND i586 that do not have "32bit" in their name ...
doesn't "solvable_name" ONLY parse the package_name filed? or does it, also, parse the arch field?
thanks!
I search and you are right, some package haven't 32-bit in it's name. So for ensure that no i386,i586 or i686 arch is installed add to your locks file this: solvable_arch: i386 solvable_arch: i586 solvable_arch: i686 But because this lock a lot of packages expect some performance problems. Josef -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hi, On Tue, 27 May 2008, Josef Reidinger wrote:
I search and you are right, some package haven't 32-bit in it's name. So for ensure that no i386,i586 or i686 arch is installed add to your locks file this:
solvable_arch: i386 solvable_arch: i586 solvable_arch: i686
But because this lock a lot of packages expect some performance problems.
It's probably quicker if written as: solvable_arch: i?86 (match_type needs to be glob then, which I think is the default). Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Matz wrote:
Hi,
On Tue, 27 May 2008, Josef Reidinger wrote:
I search and you are right, some package haven't 32-bit in it's name. So for ensure that no i386,i586 or i686 arch is installed add to your locks file this:
solvable_arch: i386 solvable_arch: i586 solvable_arch: i686
But because this lock a lot of packages expect some performance problems.
It's probably quicker if written as:
solvable_arch: i?86
(match_type needs to be glob then, which I think is the default).
Ciao, Michael.
hmm, I don't think quicker, because bottleneck is locking many package (almost half for internet sources). I test it now and speed is almost same. Default match_type is substring not glob, so you must write this: solvable_arch: i?86 match_type: glob btw now I improve wiki for this format, so I hope it everyone better understood it. Josef -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (4)
-
josef reidiner -
Josef Reidinger
-
Michael Matz -
snowcrash+opensuse