1 Aug
2012
1 Aug
'12
2:47 a.m.
Why does the script need to know this directory? If
the
script depends on a specific binary included with Trinity, I think a more
suitable error would be "... not found", which would indicate that
this binary needs to be in the PATH environment.
The information is not always dependably knowable. For the same reason starttde checks and
sets the same type of information if not discoverable in the user's environment.
Just a suggestion to run the right command as root
seems
appropriate. Something along the lines of:
Some files in your Trinity profile cannot by modified.
(Ideally a list would appear as well.) Please run "r14-xdg-update --profile
/home/julius/.trinity" as root to finish updating the
profile. (In case the --profile parameter would be used to specify a
profile.)
In the latest update I attempted to support automated execution and running as root.
Now (without me doing any manual changes), the script
completes
successfully. Somehow it seems to miss the
/home/julius/.trinity/share/apps/konqsidebartng/webbrowsing/entries/*.desktop
files now, because they are still owned by root and also still contain
X-KDE.
Hopefully the latest version does not miss those files, or any files owned by root.
I updated the script in commit 31f926d9.
You now can run as root against any directory. There is a short help notice at the
beginning of the script how to do that. In your case, run the script under your normal
user account. Hopefully you'll see an error message that the aforementioned files were
not updated. The stdout message will list a text file that list the problematic files.
Then with those files still owned by root, run the script as root and the files should
then update.
Darrell