Packagin query

[Srimalik]

Hi,
I have a package which can be installed on PA as well as IA.
architecture HP-UX_B.11.23_IA/PA

The binaries will run using aries on IA systems.

Now I have to add a coreq for patch PHSS_35528 to this package.

I am not able to figure out how to do this. : (

Can I add it directly as a normal coreq and it will work. ( swinstall on PA will simply ignore the patch as it does not have anything for IA, and on IA the patch will be installed)

NOTE: both the patch and our package are present at same location

OR

Is there some Syntax to specify a coreq such that it comes only in effect when the package is being installedon an IA system.
Something like :
corequisite IA/PHSS_35528 OR corequisite PHSS_35528,IA


Thanks
Sri

[whiteknight]

Sri,

It will work, even though it is for IA to install, it will not do any harm to the system to PA if this patch install.

WK

[Srimalik]

Hi, WK

I added the patch as a corequisite and tried to install the package on a PA system it failed with error as the dependency for the patch could not be resolved.

ERROR: "pa-hp-01:/": The software dependencies for 1 products or
filesets cannot be resolved.

Depot location had both the patch and my package. It simple ignored the patch as it is no ment for PA and gave the dependecy error.

What about the my second option Is there a syntax available to specify a dependency coupled with architechture?

Regards
Sri

[Dennis Handly]

>Now I have to add a coreq for patch PHSS_35528 to this package.

Do you know you really need that patch?

>Can I add it directly as a normal coreq and it will work?

No, as you found out on PA.

>Is there some Syntax to specify a coreq such that it comes only in effect when the package is being installedon an IA system. Something like:
corequisite IA/PHSS_35528 OR corequisite PHSS_35528,IA

Exactly, something like that. :-)

If you can take apart the linker patch, you'll see where I had to add a conditional dependency on Aries.
http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_37201

I don't see in on the above link. I'll have to get it to you when I get to work.

[Srimalik]

Hi, Dennis

Yes, I am sure that I need this patch for our PA binaries to run in emulation mode on IA.

I added this to the psf ( just copied stuf from the INDEX file of the patch you gave)

corequisites PHSS_35528,fa=HP-UX_B.11.31_IA

but its still not working :(, am I doing something wrong ?

Thanks
Sri

[Srimalik]

the added line is
corequisites PHSS_35528,fa=HP-UX_B.11.23_IA

and its not working :(.
I could not find any documentation to specify these kind of dependencies from Google. :(.

Dannis, Could you please point me to the related docs also?

-Sri

[Srimalik]

Apologies for the typo in your name Dennis. :)

[Dennis Handly · Accepted solution]

>but its still not working :(, am I doing something wrong?

Naturally, I said "something like that". :-)

>I could not find any documentation to specify these kind of dependencies from Google. :(.
>Could you please point me to the related docs also?

I couldn't find it last night. I don't think there is any external documentation with that info.

corequisite PHSS_35528.CORE2-SHLIBS,fa=HP-UX_B.11.23_IA | OS-Core.CORE2-KRN,fa=HP-UX_B.11.23_PA

The above should be one long line:
corequisite A | B

Where OS-Core.CORE2-KRN,fa=HP-UX_B.11.23_PA is the official "dummy" entry for PA. And similarly for _IA. This fileset is always there.

[Srimalik]

Thanks Dennis

It is working for PA system I have not tested it on a IA machine though. But looking at the technique followed I am sure it will work on IA as well.

What would you say about using OS-Core.CORE-KRN Instead of OS-Core.CORE2-KRN ?

In other words, are there any specific reasons to choose OS-Core.CORE2-KRN and NOT OS-Core.CORE-KRN?

Thanks
Sri

[Dennis Handly]

>What would you say about using OS-Core.CORE-KRN Instead of OS-Core.CORE2-KRN?
>In other words, are there any specific reasons to choose OS-Core.CORE2-KRN

Because that is what the internal document says to use. And even after we used that where were warnings from our patch tools. So that fileset may be hardcoded to fix that new issue.