Daniel Macks wrote:
On Wed, Oct 05, 2005 at 09:25:37AM +0200, Martin Costabel wrote:
There has been a bug report on this for a long time (#1020637). The
problem is that the pathsetup script, when run automatically by the
installer, sometimes suffers from a split personality syndrome: In the
middle of its execution, it seems to forget that it runs as $USER and
starts thinking it is root. Therefore it creates ~/.profile with root as
owner (but in the correct home directory of $USER) and worse, when it
tests whether the new setting works, it does the test as root and
concludes that it doesn't work.
The only thing usually necessary to repair this is to run
sudo chown $USER ~/.profile
after the installation.
If the file is being created in the correct place, we know $HOME is
not getting corrupted. That means we can check its owner, then chown
the dotfile acordingly and make sure we're running under that user
when doing the test.
I have now checked a fixed version of pathsetup.sh.in into CVS, so that
it will be used in the next binary installer. It turned out that the two
problems that were often observed - wrong ownership of ~/.profile and a
false failure message - were completely unrelated. I don't know why this
worked in earlier cases; perhaps different bash versions or something.
--
Martin
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
