| Line | |
|---|
| 1 | 2004-05-25 stephand
|
|---|
| 2 |
|
|---|
| 3 | in order to be able to use the same spec files both on SLES8 and SL 9.0,
|
|---|
| 4 | the macro %perl_process_packlist must be made available on SLES8:
|
|---|
| 5 |
|
|---|
| 6 | - copy the macro definition of %perl_process_packlist from a SL 9.0
|
|---|
| 7 | file /usr/lib/rpm/suse_macros to the new file /usr/lib/rpm/sc_macros_sles8
|
|---|
| 8 | - %perl_process_packlist depends on the macros %perl_vendorlib and
|
|---|
| 9 | %perl_vendorarch which are missing in SLES8. Copy them from a SL 9.0
|
|---|
| 10 | file /usr/lib/rpm/macros to /usr/lib/rpm/sc_macros_sles8 on SLES8
|
|---|
| 11 | - finally add /usr/lib/rpm/sc_macros_sles8 to the definition of macrofiles
|
|---|
| 12 | (search for the line beginning with "macrofiles:")
|
|---|
| 13 | in /usr/lib/rpm/rpmrc on SLES8
|
|---|
| 14 |
|
|---|
| 15 | But this does not help us if we are using a chrooted build environment,
|
|---|
| 16 | because then /usr/lib/rpm/ all comes from the rpm rpm-package.
|
|---|
| 17 | Better approach is to create spec-files which determine the current
|
|---|
| 18 | OS and do the right things based on that. The macro %suse_version can
|
|---|
| 19 | be used for that. There exist macros called %ul_version and %sles_version
|
|---|
| 20 | but if we use them, we probably run into problems on norma SL systems.
|
|---|
| 21 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
