Date: Thu, 22 Oct 1998 11:23:31 -0700 From: bmah@CA.Sandia.GOV (Bruce A. Mah) To: Kris Kennaway <kkennawa@physics.adelaide.edu.au> Cc: John Saunders <john.saunders@scitec.com.au>, FreeBSD current <freebsd-current@FreeBSD.ORG> Subject: Re: Package upgrade check program Message-ID: <199810221823.LAA10521@stennis.ca.sandia.gov> In-Reply-To: Your message of "Thu, 22 Oct 1998 15:19:12 %2B0930." <Pine.OSF.4.05.9810221516120.11811-100000@bragg>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_132680773P
Content-Type: text/plain; charset=us-ascii
If memory serves me right, Kris Kennaway wrote:
> On Thu, 22 Oct 1998, John Saunders wrote:
>
> > With everybody hot into upgrading to 3.0, I thought I would
> > throw this script in that I have been working on the last
> > couple of days (bit at a time). This script suggests upgrades
> > to installed packages. I'm continuing to work on a version
> > that will do the upgrade for you (after prompting of course).
>
> Bruce Mah posted a similar script to one of the mailing lists a few months
> ago- search the mailing list archives for pkg_version. IMO it would be good t
> o
> get something like this into the base system, or perhaps as a port (a la
> mergemaster). Perhaps you could get together and combine your good ideas and
> submit something to the ports team.
I did submit pkg_version as a new port (ports/7777), but it probably wasn't
high up enough on anyone's priority list to commit, with all of the
3.0-RELEASE stuff happening about the same time. Since then, it needs a
little tweak to make it find perl correctly (i.e. use ${PERL}). I haven't
done a follow-up yet, because I just now got a 3.0-RELEASE machine up to test
things on.
I'm a little leery of the "automatic upgrades" part, and I never had any plans
to put it into pkg_version. In my experience it's too easy to get really
confused by having multiple versions of a port installed (e.g.
ssh-1.2.2[256]), and you sometimes can't predict all these due to port
dependencies. Moreover, different packages have various degrees of
co-existence tolerance, and the INDEX file can't really express this
information well. This paragraph isn't criticism of the ports system; it's a
hard problem. I'm not sure what the right solution is.
So I just took the easy way out...pkg_version just generates a report (as
John's pkg_check does), and it's up to the user to figure out what to do.
Right now it does pretty much everything that I personally need it to do.
John, what else (in addition to automatic upgrades) do you have in mind for
pkg_check?
Bruce.
--==_Exmh_132680773P
Content-Type: application/pgp-signature
-----BEGIN PGP MESSAGE-----
Version: 2.6.2
iQCVAwUBNi94I6jOOi0j7CY9AQE5VgP/fdu9hBbDysGOaOeF6YTQiUlzsmuxmfKN
Oe5TD2HvnEPFGZY0BBByKNEloGcyFOyYteQyxCZMl3s5wzSalRDNO89mSH4nyihS
ZlgDXorpX6Fd+idhYWNcxybfHUQViWjWX9JPWvKv22pKZzbErCOcGEPV3nzn0dUB
YOTP90ZYDLo=
=xnEd
-----END PGP MESSAGE-----
--==_Exmh_132680773P--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810221823.LAA10521>