Mailinglist Archive: yast-devel (191 mails)
| < Previous | Next > |
Re: [yast-devel] extra-packages
- From: Andreas Jaeger <aj@xxxxxxx>
- Date: Thu, 20 Mar 2008 16:17:46 +0100
- Message-id: <87tzj1bf1h.fsf@xxxxxxx>
Lukas Ocilka <lukas.ocilka@xxxxxxx> writes:
Remove completely, axp is not supported anymore.
Why think most of these should be done in another way. sudo looks wrong
and the rest is hardware support that can be handled differently.
Does yast2-installation really need this - or can we install it via patterns?
Why does yast2-installation need numactl? It should be installed via patterns.
Andreas
--
Andreas Jaeger, Director Platform / openSUSE, aj@xxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger napsal(a):
Lukas Ocilka <lukas.ocilka@xxxxxxx> writes:
But finally I've found that some currently NOARCH packages use several
"#if defined(__$arch__)" in that extra-packages file. So moving the
content to "Suggests: $package" would mean transforming some NOARCH
packages to architecture-dependent just because of suggested packages :(
Are those requirements still current and correct? Could you give us the
list, please?
File attached.
For simplicity only those "Suggested:$packagename" that are marked
architecture-dependent are listed there. For instance yast2-installation
has some more but they appear to be NOARCH, so they don't change anything.
NOARCH YaST packages affected:
* yast2-installation
* yast2-samba-client
* yast2-kerberos-client
Lukas
##########################
### yast2-installation ###
##########################
#if defined(__axp__)
yast2-installation:milo
yast2-installation:aboot
yast2-installation:cpml_ev5
yast2-installation:cpml_ev6
#endif
Remove completely, axp is not supported anymore.
#if defined(__ppc__) || defined(__ppc64__)
yast2-installation:ibmsis
yast2-installation:scsi
yast2-installation:mouseemu
yast2-installation:pbbuttonsd
yast2-installation:powerprefs
yast2-installation:mol
yast2-installation:sudo
yast2-installation:powerpc-utils
#endif
Why think most of these should be done in another way. sudo looks wrong
and the rest is hardware support that can be handled differently.
#if defined(__ia64__)
yast2-installation:fpswa
#endif
Does yast2-installation really need this - or can we install it via patterns?
#if defined(__x86_64__)
yast2-installation:numactl
#endif
Why does yast2-installation need numactl? It should be installed via patterns.
##########################
### yast2-samba-client ###
##########################
#if defined(__x86_64__) || defined(__s390x__) || defined(__ppc__)
yast2-samba-client:samba-client-32bit
yast2-samba-client:samba-winbind-32bit
yast2-samba-client:krb5-32bit
#endif
#if defined(__ia64__)
yast2-samba-client:samba-client-x86
yast2-samba-client:samba-winbind-x86
yast2-samba-client:krb5-x86
#endif
#if defined(__ppc64__)
yast2-samba-client:samba-client-64bit
yast2-samba-client:samba-winbind-64bit
yast2-samba-client:krb5-64bit
#endif
#############################
### yast2-kerberos-client ###
#############################
#if defined(__ia64__)
yast2-kerberos-client:krb5-x86
yast2-kerberos-client:pam_krb5-x86
#endif
#if defined(__ppc64__)
yast2-kerberos-client:krb5-64bit
yast2-kerberos-client:pam_krb5-64bit
#endif
#if defined(__x86_64__) || defined(__s390x__) || defined(__ppc__)
yast2-kerberos-client:krb5-32bit
yast2-kerberos-client:pam_krb5-32bit
#endif
Andreas
--
Andreas Jaeger, Director Platform / openSUSE, aj@xxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
| < Previous | Next > |