Hello.

I am running Solaris 8 x86 (required here). I had previously installed
Mozilla Firefox, Gaim, rdesktop and vncviewer from blastwave.org and
they are great and work fine.


So I decided to install the openssh package from CSW with:
# pkg-get -i openssh

It installed fine, and it also installed all its dependecies. I tested
it for several days, and finally I decided to uninstall it, with the
command:

# pkg-get -r openssh

The package got removed flawlessley. However, and this is the point, I
did not jot down all the dependencies the package installed, so this is
my question: How can I find out which dependencies had this package
installed on my system, in order to manually remove them?

(I can not simply remove all the CSW* packages from my system, as I am
using several which were installed before I tried openssh, and which I
want to keep, like Firefox, rdesktop, Gaim, etc.)

Thank you very much for reading.

Regards.

z80 <z80@ya.com> writes:

> Hello.
>
> I am running Solaris 8 x86 (required here). I had previously installed
> Mozilla Firefox, Gaim, rdesktop and vncviewer from blastwave.org and
> they are great and work fine.
>
>
> So I decided to install the openssh package from CSW with:
> # pkg-get -i openssh
>
> It installed fine, and it also installed all its dependecies. I tested
> it for several days, and finally I decided to uninstall it, with the
> command:
>
> # pkg-get -r openssh
>
> The package got removed flawlessley. However, and this is the point, I
> did not jot down all the dependencies the package installed, so this
> is my question: How can I find out which dependencies had this package
> installed on my system, in order to manually remove them?

go to http://www.blastwave.org/packages.php/openssh where you can see
the list of dependencies for the above mentioned package.

> (I can not simply remove all the CSW* packages from my system, as I am
> using several which were installed before I tried openssh, and which I
> want to keep, like Firefox, rdesktop, Gaim, etc.)
>
> Thank you very much for reading.
>
> Regards.

--
the true email address is encoded in an attempt to minimize spam.
pass csryrpna ng npz qbg bet through http://www.rot13.com/

In article <d12hgg$5lo$1@news.ya.com>,
z80 <z80@ya.com> writes:
> Hello.
>
> I am running Solaris 8 x86 (required here). I had previously installed
> Mozilla Firefox, Gaim, rdesktop and vncviewer from blastwave.org and
> they are great and work fine.
>
>
> So I decided to install the openssh package from CSW with:
> # pkg-get -i openssh
>
> It installed fine, and it also installed all its dependecies. I tested
> it for several days, and finally I decided to uninstall it, with the
> command:
>
> # pkg-get -r openssh
>
> The package got removed flawlessley. However, and this is the point, I
> did not jot down all the dependencies the package installed, so this is
> my question: How can I find out which dependencies had this package
> installed on my system, in order to manually remove them?
>
> (I can not simply remove all the CSW* packages from my system, as I am
> using several which were installed before I tried openssh, and which I
> want to keep, like Firefox, rdesktop, Gaim, etc.)
>
> Thank you very much for reading.


See http://www.blastwave.org/packages.php/openssh

(assuming you had the same version of their openssh package that
describes; dependencies _can_ change at different versions of their
packages, see final paragraph below)

However, it's entirely possible that other packages share dependencies
on those; zlib for sure, probably one or more others too. You could
follow the links for those packages and see what depends on them; or
you could try something like:

for pkg in CSWkrb5lib CSWzlib CSWtcpwrap CSWossl
do
if grep "${pkg}" /var/sadm/pkg/CSW*/install/depend >/dev/null; then
echo "${pkg} has dependencies - do not remove!"
fi
done


(not precise, but probably good enough); in my case, all four packages
had other (I didn't have blastwave openssh installed) dependencies.


Just to make it a little more interesting for other folks, it's my
impression that blastwave has been splitting apart packages that had
certain dependencies built in to them, so that there's more nearly one
package per separately distributed open-source component (or something
like that). In any case, I've had occasions where I was simply updating
an existing package, and the new package itself was much smaller, but it
dragged down a whole bunch of new dependencies, so that the total certainly
wasn't smaller (by itself; perhaps if something else shared some of those
dependencies...).



--
mailto:rlhamil@smart.net http://www.smart.net/~rlhamil

Lasik/PRK theme music:
"In the Hall of the Mountain King", from "Peer Gynt"

Richard L. Hamilton wrote:
> In article <d12hgg$5lo$1@news.ya.com>,
> z80 <z80@ya.com> writes:
>
<snip>

>
> Just to make it a little more interesting for other folks, it's my
> impression that blastwave has been splitting apart packages that had
> certain dependencies built in to them, so that there's more nearly one
> package per separately distributed open-source component (or something
> like that). In any case, I've had occasions where I was simply updating
> an existing package, and the new package itself was much smaller, but it
> dragged down a whole bunch of new dependencies, so that the total certainly
> wasn't smaller (by itself; perhaps if something else shared some of those
> dependencies...).
>

We tend to split packages into run-time and full/the rest package. One
example is MySQL; linking/using the MySQL client libraries only really
requires the shared libraries, and not the full database engine, thus
MySQL is split into two packages. If you run pkg-get -i mysql4 it will
also install the run-time...

/A