Glenn Lagasse wrote: > * Shawn Walker (swalker at opensolaris.org) wrote: >> ss-dev and gcc-dev will both cause SUNWhea to be installed: >> >> pkg install -nv ss-dev >> ... >> None -> pkg:/SUNWhea at 0.5.11,5.11-0.111:20090331T082919Z >> ... >> >> >> pkg install -nv gcc-dev >> ... >> None -> pkg:/SUNWhea at 0.5.11,5.11-0.111:20090331T082919Z >> ... > > Interesting. Why doesn't SUNWhea then show up as part of this command? > > glagasse at shire:~$ pkg contents -r -t depend -o fmri gcc-dev > FMRI > SUNWaconf at 2.61-0.111 > SUNWbison at 2.3-0.111 > SUNWcvs at 1.12.13-0.111 > SUNWflexlex at 2.5.33-0.111 > SUNWgcc at 3.4.3-0.111 > SUNWgdb at 6.3-0.111 > SUNWgmake at 3.81-0.111 > SUNWgnu-automake-110 at 1.10-0.111 > SUNWgnu-automake-19 at 1.9.6-0.111 > SUNWlibtool at 1.5.22-0.111 > SUNWmercurial at 1.1.2-0.111 > SUNWsprot at 0.5.11-0.111 > SUNWsvn at 1.4.3-0.111 > > It appears that SUNWhea is a dependancy of SUNWgcc. Is there something > I can modify in the pkg contents command that will pick up 'all' > dependencies (like SUNWhea when talking about gcc-dev for instance)?
Contents is only for showing you the *contents* of a specified package :) > Basically, I want to see 'sub-depends' in the same listing. Is this > possible? So, using the example above, the list would also include > SUNWhea because SUNWgcc depends on it. Not at this time. I'm not certain where we would provide this information... > I can get something like this output using pkg install -nv, but only if > I haven't installed the package yet. In my case, I've already installed > gcc-dev and so pkg install -nv gcc-dev doesn't return anything. Correct. I don't have a good answer for you, but I do know that contents probably isn't the right place to show it. I filed this at defect.opensolaris.org: 8124 functionality to obtain full dependency list (direct and indirect) desired Cheers, -- Shawn Walker
