Date: Sat, 30 Sep 2000 23:52:28 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp> Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: (Semi-)automatic update of installed ports (was: Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior) Message-ID: <14806.49932.529722.3304@guru.mired.org> In-Reply-To: <14806.49271.166621.26482Z@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> <14806.12932.647387.503859@guru.mired.org> <14806.49271.166621.26482Z@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 Sat, 30 Sep 2000 13:35:48 -0500 (CDT), Mike Meyer <mwm@mired.org> 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 :-). <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14806.49932.529722.3304>