Mark,
Sorry for the confusion. I first was using "c++" but the data I gave
you the last time was again
"fortran". Let me keep it to "c++" below.
On 10/20/2011 12:20 PM, Mark J. Nelson wrote:
On 10/20/11 10:00, Kristin Beatty wrote:
On 10/20/2011 11:28 AM, Mark J. Nelson wrote:
Are you trying to manually maintain dependencies AND use pkgdepend to
automatically generate dependencies?
no
If so, then you should stick with pkgdepend, and not put the manual
entries there in the first place.
If not, then the generation of duplicate dependencies is a bug.
But the fact that one of the backend dependencies is versioned and the
other isn't suggests that you're supplying the non-versioned one explicitly.
Manifest for c++ shows:
depend fmri=pkg:/solarisstudio/solarisstudio12.2/cc type=require
depend fmri=pkg:/solarisstudio/solarisstudio12.2/backend type=require
depend fmri=pkg:/solarisstudio/solarisstudio12.2/c++-libs type=require
After running "pkgdepend resolve -s .pre-dedup -m manifest"
manifest.pre-dedup shows:
depend fmri=pkg://solarisstudio/solarisstudio12.2/[email protected]
type=require
depend fmri=pkg:/solarisstudio/solarisstudio12.2/backend type=require
depend fmri=pkg:/solarisstudio/solarisstudio12.2/c++-libs type=require
depend fmri=pkg:/solarisstudio/solarisstudio12.2/cc type=require
For some reason resolve is adding another backend with a dependency. I
could remove
all the @12.2-0.x entries but then I run into a problem like in fortran.
Fortran manifest:
depend fmri=pkg://solarisstudio/solarisstudio12.2/backend type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/f90-libs type=require
Fortran manifest.pre-dedup after "pkgdepend resolve": (Note addition of
math-libs)
depend fmri=pkg://solarisstudio/solarisstudio12.2/backend type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/[email protected]
type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/f90-libs type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/[email protected]
type=require
You state I can remove the "depends" from the manifest list but we have to
have them in there to insure that bug fixes that has dependencies on
other packages
get updated too.
On 10/20/11 07:05, Kristin Beatty wrote:
I am currently building on 171 and trying to remove multiple package
dependencies:
The manifest line contains:
depend fmri=pkg://solarisstudio/solarisstudio12.2/backend type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/[email protected]
type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/c++-libs type=require
depend fmri=pkg://solarisstudio/solarisstudio12.2/cc type=require
One solution was to use the following line: sed
"/^depend.*solarisstudio12.2.*@/d"
but that caused problems when it removed all entries for a package when
there
was only one entry as:
depend fmri=pkg://solarisstudio/solarisstudio12.2/[email protected]
type=require
I am trying to automate the process and I thought I could get away with
just having
two identical depend entries but pkglint fails as shown below:
Lint engine setup...
1 ... 2 ... 3 ... 4 ... Done
Starting lint run...
ERROR pkglint.manifest005.2 duplicate depend actions in
pkg://solarisstudio/solarisstudio12.2/[email protected],5.11-0.0
solarisstudio12.2/backend
Any recommendations?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
