On Monday, September 23, 2002, at 12:39 AM, Ken Williams wrote:
> > On Monday, September 23, 2002, at 03:08 PM, Puneet Kishor wrote: > >> two odd things I have noticed since clean upgrading to OS X 10.2 >> >> 1. path settings seem to be changed. one examples -- (1) Dan Kogai's >> lifesaving psync sitting under /usr/local/bin is not reachable >> anymore. A quick look at setenv shows that my PATH is just >> /bin:/sbin:/usr/bin:/usr/sbin so obviously psync will not be >> reachable now from my home directory. Of course, I can add >> /usr/local/bin to PATH, but what curious minds want to know is how >> did this happen? It worked fine earlier, and I don't recall ever >> adding /usr/local/bin to the path... so how did it work earlier? or >> conversely, why did it break now? > > In 10.1.5, the file /usr/share/init/tcsh/login (which is executed at > login) contains this: > > set path = ( \ > ~/bin \ > /usr/local/bin /usr/bin /bin \ > /usr/local/sbin /usr/sbin /sbin \ > ) > > So that must have changed in 10.2. yes, and then some... first, there is no /usr/share/init/tcsh/login anymore... in fact, there is no init anymore. Instead, there is /usr/share/tcsh/examples/login which looks like what you wrote above. I'm gonna copy this login file to my ~/.login and methinks that should take care of things, no? But I wonder what all tcsh is executing on a system-wide basis, not just specific to my account. > > >> 2. cpan did something strange -- I fired up cpan and it promptly >> reminded me that I should upgrade cpan itself as well as libnet. I >> dutifully upgraded cpan to 1.63 and reloaded, and then asked it to >> upgrade libnet. Lo and behold... I see cpan is trying to download 11 >> Mb of Perl 5.8.0, not something I asked for. > > This is THE MOST ANNOYING thing CPAN does, and although everyone > always *assures* me it's been fixed, it continues to happen. > > >> I ctr-c-ed out and it seems to have installed libnet ok. Could anyone >> please reassure me that cpan didn't try to go in and screw around >> with my stock Apple Perl 5.6.0 install... that is not something I >> want at all. > > That's exactly what it tried to do. It tried to install 5.8.0. > Luckily, since the process takes so long (download, build install), > you probably caught it in time and no harm was done. > phew! I understand that CPAN tries to install all the dependent modules, etc., but heck, trying to install the motherlode itself is a bit of a stretch. And, I wonder how it does it... I mean, CPAN is written in perl, so, in my case, uses the perl5.6.0 compiler/interpreter... so here we have, the 5.6.0 compiler/interpreter trying to install the 5.8.0 version. Surely that should cause some train wrecks along the way. anyway, I do appear to be safe... I broke out early enough. Thanks, pk/
