[csw-maintainers] Dependencies on SUNW packages (was: newpkgs libslp1, openslp_devel)
Maciej (Matchek) Blizinski
maciej at opencsw.org
Tue Dec 21 19:41:23 CET 2010
No dia 21 de Dezembro de 2010 17:12, Philip Brown <phil at bolthole.com> escreveu:
> On 12/21/10, Maciej (Matchek) Blizinski <maciej at opencsw.org> wrote:
>>
>> I know that we don't list the SUNW dependencies, because we can't
>> install them, that's fair enough. But we probably want to ensure that
>> our packages work when installed. What's our strategy for CSW
>> packages with SUNW dependencies?
>>
>
> wanted to potentially clear an ambiguity here:
>
> first of all, I'm curious what you meant by "list". were you speaking
> webpage, or actual depend file?
I meant listing them in the depend file, declaring the dependency.
> secondly... if we have a dependancy on a semi-'rare' sun package... we
> can and SHOULD put in SUNW packages as a dependancy.
> We dont usually bother having SUNWxxx in depend, because they are
> probably installed anyway.
I assumed that not depending on SUNW packages was for a different
reason, but I guess we never discussed it. I thought that we don't
depend on SUNW because, for example, /usr/lib/sparcv9/libz.so.1 is in
SUNWzlibx on Solaris 9 and in SUNWzlib on Solaris 10. If you depend
on SUNWzlibx, you can't install on Solaris 10 because of an unmet
dependency.
It's just an example, there are more of these files. Here's an
example list for sparc[1].
[1] http://buildfarm.opencsw.org/~maciej/files-in-different-packages.txt
More information about the maintainers
mailing list