[yast-devel] using lib versus lib64 versus lib32 in YCP
Hello, is there a generic way in YCP to get the right default libdir (/usr/lib/ versus /usr/lib64/ versus /usr/lib32/) for the various architectures? For background information see https://bugzilla.novell.com/show_bug.cgi?id=464683 I must call /usr/$(libdir)/cups-autoconfig/cups-autoconfig I like to avoid a longer sequence of testing each individual architecture which we currently have for SLE11 (i586, x86_64, s390, s390x, ppc, ppc64, ia64). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thu, Jan 22, 2009 at 05:47:19PM +0100, Johannes Meixner wrote:
is there a generic way in YCP to get the right default libdir (/usr/lib/ versus /usr/lib64/ versus /usr/lib32/) for the various architectures?
No. We have Directory.ycp for similar purposes, but YCP code simply should not need to care about plain libdir.
For background information see https://bugzilla.novell.com/show_bug.cgi?id=464683
I must call /usr/$(libdir)/cups-autoconfig/cups-autoconfig
IMO that is a packaging bug of cups-autoconfig.
I like to avoid a longer sequence of testing each individual architecture which we currently have for SLE11 (i586, x86_64, s390, s390x, ppc, ppc64, ia64).
Oh well. How about searching lib64 lib32 and lib in sequence? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Jan 23 10:18 Martin Vidner wrote (shortened):
On Thu, Jan 22, 2009 at 05:47:19PM +0100, Johannes Meixner wrote:
I must call /usr/$(libdir)/cups-autoconfig/cups-autoconfig
IMO that is a packaging bug of cups-autoconfig.
I agree because - as far as I know - executables should be in a .../bin/... directory. I assume there is nothing in YCP which lets me fix packaging bugs on the fly? ;-)
I like to avoid a longer sequence of testing each individual architecture which we currently have for SLE11 (i586, x86_64, s390, s390x, ppc, ppc64, ia64).
Oh well. How about searching lib64 lib32 and lib in sequence?
This is also my fallback idea if there is no "elegant" way in YCP so that I will implement it this way. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (2)
-
Johannes Meixner -
Martin Vidner