Seigo Tanimura writes:
> On Sat, 30 Sep 2000 13:35:48 -0500 (CDT),  Mike Meyer <[EMAIL PROTECTED]> said:
> Mike> Seigo Tanimura writes:
> >> 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.
> Mike> Frankly, I'm not really interested in *detecting* such things. A tool
> Mike> that would 1) save tarballs of *all* installed ports; 2) uninstall
> Mike> them all; then 3) rebuild and install them all, with a report about
> Mike> failures would make me happy.
> How do you rebuild a port automatically if you want to hack the
> configure parameter or make variables of the port?

Since that information isn't currently stored, you have to do it by
hand :-(. Of course, you also have to *guess* what port corresponds to
an installed package, as the information about which ports collection
a package came from is lost as well. It's not clear that the port
names are globally uniq, either.

If it were easy, I'd've done it myself :-).


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to