Laszlo (Laca) Peter wrote:
> Baban,
>
> Yes, pkgbuild uses pkginfo to look up packages. pkginfo reports
> both SVr4 packages and IPS packages with a legacy action.
> All OpenSolaris /release and /dev packages have legacy actions and
> pkgbuild also adds legacy actions to its manifests so using pkginfo
> this way works fine on OpenSolaris. What this gives us is
> compatibility with Solaris 10 and Nevada at the spec file level.
> You can build the same spec without having to use different package
> names on OpenSolaris, even if the IPS package name is different.
> pkgbuild will take care of translating the SVr4 package name
> to an IPS package name, by searching for a matching legacy action.
>
> Does this answer your concern?
>
Yes. Thanks.
The failure on my system was because one of the build dependencies was
already installed on my system and I guess was build by a older version
of pkgbuild that I assume did not support legacy action. I re-built the
pkg using the newer version of pkgbuild and re-installing it fixed the
issue.
--Baban
> Laca
>
> On Tue, 2009-03-17 at 01:47 -0700, Baban Kenkre wrote:
>
>> I've some "BuildRequires" in my spec file but pkgbuild fails because it
>> is unable to find the build dependencies although they are installed on
>> my system.
>>
>> A cursory look of pkgbuild.pl shows
>> sub check_dep
>> } elsif ($os eq "solaris") {
>> `/usr/bin/pkginfo -q '$pkg.*'`;
>> if ($? != 0) {
>> return 0;
>> }
>>
>> Is it true that pkgbuild only uses pkginfo command to check for build
>> dependencies on solaris systems. If this is true and assuming that the
>> jucr build system is an opensolaris system, is support for checking IPS
>> pkgs in the works ?
>>
>> Thanks,
>> Baban
>> _______________________________________________
>> sourcejuicer-discuss mailing list
>> sourcejuicer-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/sourcejuicer-discuss
>>
>
>
