Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Sep 2000 13:35:48 -0500 (CDT)
From:      Mike Meyer <mwm@mired.org>
To:        Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp>
Cc:        current@FreeBSD.ORG
Subject:   Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
Message-ID:  <14806.12932.647387.503859@guru.mired.org>
In-Reply-To: <14805.63360.137164.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp>
References:  <20000906151431.A26152@hamlet.nectar.com> <14798.4853.288090.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <20000924100812.A23848@spawn.nectar.com> <200009281350.WAA23538@bunko> <20000928115555.D42464@spawn.nectar.com> <14805.63360.137164.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
Seigo Tanimura writes:
> On Thu, 28 Sep 2000 11:55:55 -0500,
>   "Jacques A. Vidrine" <n@nectar.com> said:
> >> It would also be helpful for us to (semi-)automatically update old
> >> binaries installed by ports. (I have been trying this for a couple of
> >> days)
> Jacques> Personally I don't want sysinstall or make world to touch my ports.
> Jacques> But a tool to do this would be great.
> Completely automatic update of installed ports is acutally difficult
> because we cannot get to know the language or required toolkit from
> the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw
> and timidity++-tcltk) We can still detect and enumerate the ports that
> possibly installed old binaries, and decide which of the ports listed
> up to update.

Ah - there's *two* meanings for "old" here. If you were talking about
binaries installed by out-of-date ports, that's easy:
weekly_status_pkg in the periodic subsystem will do that for
you. However, I believe you were talking about binaries that may have
been built from a current port against an out-of-date system.

Frankly, I'm not really interested in *detecting* such things. A tool
that would 1) save tarballs of *all* installed ports; 2) uninstall
them all; then 3) rebuild and install them all, with a report about
failures would make me happy.

That way, I'd know that all the ports were built against the current
system, which would make me feel much safer.

	<mike



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?14806.12932.647387.503859>