On Sunday 07 September 2003 06:22, Kim Woelders wrote: > As non-root, doing "chown -R root <anything>" will fail. > The themes *are* special. They are unpacked from tarballs, and if root > does that the U/GID's are preserved, so we have to set them as we want > them. I don't think there is much point in doing the "chown -R" as a > non-root user, but the construction does avoid having to figure out wheter > or not we are root in some other way.
true enough, my fault for missing that obvious note ;) > I don't quite follow the normal user temporary install thing. > Are you saying that > # make install > behaves differently after doing > $ make install DESTDIR=$PWD/test i do things in odd ways, forget that note ... > The only trouble I see after doing "make install" as root is that the > theme file group ID's are not root. > Maybe we should do: > if [ "$USER" = "root" -o "$USER" = "" ]; then \ > chown -R root $(DESTDIR)$(ethemedir); \ > chgrp -R root $(DESTDIR)$(ethemedir); \ > fi my e-mail stemmed from a case where $USER was messed up, and thus caused the `make install` to fail since $USER did not actually exist ... my first 'solution' was just to not use it (and thus try to chown everything root) but we saw how that doesnt work :) next 'solution' perhaps is to get the $USER from `whoami` or `id -un` ... $USER has a pro ... the chown can be easily manipulated via the environment ... but $USER has a very similar con ... if $USER is messed up then the chown would fail ... but then again if someone cares enough to mess around with permissions perhaps they can just do it after the fact (the fact being the install ...) -mike
pgp00000.pgp
Description: signature
