Date: Tue, 30 May 2006 20:23:25 -0500 From: Vulpes Velox <v.velox@vvelox.net> To: brain@winbot.co.uk Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Survey Message-ID: <20060530202325.1398cc84@vixen42.vulpes> In-Reply-To: <447AEA9B.6030005@winbot.co.uk> References: <20060523120100.37D2B16A54F@hub.freebsd.org> <20060523083944.H96736@eboyr.pbz> <f34ca13c0605240233t1b3555dbn39f34b4d598d5bb7@mail.gmail.com> <20060524220703.K62075@a2.scoop.co.nz> <44743358.2020304@winbot.co.uk> <20060528210403.GB8791@silverwraith.com> <447AEA9B.6030005@winbot.co.uk>
index | next in thread | previous in thread | raw e-mail
On Mon, 29 May 2006 13:35:39 +0100 Craig Edwards <brain@winbot.co.uk> wrote: > I was thinking more of the time-to-repair of a broken install, > rather than a broken python or perl program, for example if your > perl site-perl folder gets damaged, or your python compiled libs > become ABI 'incompatible' somehow (say due to a g++ upgrade?). > > In this case, both python *and* perl are pretty hard to repair > unless you know the language, and can leave a system administrator > between a rock and a hard place (reinstall, or seek an expert of > that language) > > I guess the same goes for ruby, i wouldn't know where to start in > repairing a broken ruby install... It's been awhile since I've done something stupid that fragged ruby. It was easy to fix though. I just rebuilt all the ruby stuff using portupgrade. The same thing needs done with lots of perl modules as well after perl is upgraded.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060530202325.1398cc84>