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.
_______________________________________________
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"