Date: Wed, 18 Aug 2004 21:06:11 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Henrik W Lund <henrik.w.lund@broadpark.no> Cc: freebsd-questions@freebsd.org Subject: Re: cvsup install Message-ID: <20040818200611.GA4900@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <41241D65.5010007@broadpark.no> References: <394D8FE2-F13F-11D8-8AD6-000393934006@mail.dux.ru> <41241D65.5010007@broadpark.no>
next in thread | previous in thread | raw e-mail | index | archive | help
--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Aug 18, 2004 at 08:24:21PM -0700, Henrik W Lund wrote:
> Curtis Vaughan wrote:
>=20
> >Made a big mistake today. I was reading in a book that I needed to=20
> >install cvsup for doing updates. Good. So, I started installing it. =
=20
> >Meanwhile I began perusing the FreeBSD website information about cvsup=
=20
> >and there I read, if you not using a gui, then don't install cvsup,=20
> >but cvsup-without-gui. So, is there a way to back out the cvsup which=
=20
> >I did do as it apparently has installed a lot of stuff I don't need on=
=20
> >this server.
> >Or do I have to just uninstall all those packages individually? Is=20
> >there a way then to identify which packages were installed by=20
> >installing cvsup?
> >
> >Curtis
>=20
> Greetings!
>=20
> I'd say your best bet is to install sysutils/portupgrade and use the=20
> pkg_deinstall command with the -R flag. I.e.:
>=20
> `pkg_deinstall -R cvsup'
>=20
> If you absolutely do not want any more riffraff on your box, then you=20
> must examine the output of
>=20
> `pkg_info -r cvsup'
>=20
> and pkg_delete each of the packages listed manually, then delete cvsup.=
=20
> If pkg_delete fails on any one of the packages in the list, recurse=20
> through its dependencies until it can be deleted, then proceed to the=20
> next package in the list, etc... Just be careful when traversing the=20
> dependencies. Sooner or later you might deinstall something you really=20
> want to keep, so keep your eyes open. Not all packages that cvsup=20
> depends on is required only by cvsup, and some of them were probably=20
> already installed when you installed cvsup. Like I said, your best bet=20
> is to go with the sysutils/portupgrade method.
This is generally sound advice, but unfortunately, and particularly in
the case of the cvsup ports, it pretty much misses the point.
cvsup depends on very few other ports, all of which are also commonly
dependencies of a large number of other ports:
% pkg_info -r cvsup\*
Information for cvsup-16.1h:
=20
Depends on:
Dependency: pkgconfig-0.15.0_1
Dependency: imake-6.7.0_2
Dependency: freetype2-2.1.7_3
Dependency: expat-1.95.8
Dependency: fontconfig-2.2.3,1
Dependency: xorg-libraries-6.7.0_1
In fact, almost all those dependencies are inherited indirectly
through the xorg-libraries port. The cvsup-without-gui package
doesn't have *any* dependencies. Chances are the 'pkg_deinstall -R'
method suggested will only remove the cvsup or cvsup-without-gui port.
Of course, what I've been looking at here are *run time dependencies*.
If you install cvsup from a pkg, that's all you have to bother with.
However, if you install cvsup from source code there's a whole other
swathe of dependencies that haven't yet been considered. Those are
the *build time dependencies*. In cvsup's case, those are quite
heavy: it's necessary to install a complete Modula3 compilation tool
chain:
% cd /usr/ports/net/cvsup
% make -V BUILD_DEPENDS
/usr/local/lib/m3/pkg/formsvbt/FreeBSD4/libm3formsvbt.a:/usr/ports/lang=
/ezm3
The situation has improved over time, and all that's required nowadays
is the ezm3 port. But that's a very large port, and it takes quite a
lot of effort to compile and install.
You don't need ezm3 for cvsup to work from day to day. You do need it
anytime you want to compile an update to cvsup from source. In
principal you can get round that by just using the pkg system to get
any updates, so long as you're willing to wait for a few weeks for the
updated packages to come out. Personally I'd just leave ezm3 inplace
and compile cvsup updates from source.
As for whether the OP should install cvsup or cvsup-without-gui --
either will do just fine. The advice to install the cvsup-without-gui
pkg seen in many places on the net is becuse it's a lot quicker to
install that dependency-less port than it is to install various X
libraries and other stuff. Additionally I'd install cvsup-without-gui
if I was building a server machine *without* any X windows stuff on it
at all. Otherwise, I'd just install the cvsup port. Indeed, for a
brand-new install from scratch, I tend to install cvsup-without-gui
temporarily and then use it to pull down the latest system and ports
sources. After which that port will almost immediately be overwritten
with a freshly compiled copy of the cvsup port as part of the general
process of installing all of the extra ports I need.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)
iD8DBQFBI7aziD657aJF7eIRAuEDAJ9O+XKDkF3fo6Ud6oDzsIiEfXBnPwCdGNlE
9Dkf4aDHggtksKcXrThppI8=
=kOCU
-----END PGP SIGNATURE-----
--7JfCtLOvnd9MIVvH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040818200611.GA4900>