begin quoting Jon Wahlmann as of Thu, Jan 19, 2006 at 10:53:03AM -0800: [snip] > I guess I should have clarified...
What, and miss out on all the discussion that results from creative misunderstandings? Do you want me to have no fun at all?! > Assuming you are also given permission to install tools for your own use in > "your" home directory. I have in the past compiled and installed perl in my > home directory, even when I had root permission and could install it as I > pleased under /usr/blahblahblah, just so I could test it out in a somewhat > confined environment. I tend to do this on my home machines. I compile and install a lot of stuff to /tmp or $HOME/local to check it out... which is why the tendency for a lot of software to splatter stuff all over the system is so annoying. (And why "package installers" that don't let you specify target locations are just evil. Yes, Apple, I'm looking at the GNU tools that are built with the XCode package-installer-builder.) > One could do this (once again, assuming it's ok with > the powers that be) so that it's just another tool in the specific user's > toolbox (ie. $HOME/bin). That way Lan, or whomever, can still use Perl for > their "Pattern Extraction and Reporting" needs without interfering with the > "standard toolset" provided by the organization. Yup. If $POLICY says "anything non-standard you compile and install in your home directory, and _you_ maintain it", then, well, that's policy. No worries. -- _ |\_ \| -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
