On Fri, 23 Sep 2005 15:08:33 -0500, +Alan Hicks+ wrote:

> In alt.os.linux.slackware, Guybrush Threepwood dared to utter,
>> when I'm building my own packages, for applications that
>> have no 'official' scripts, how do I know what permissions
>> to set for certain files?
>>
>> Are there some rules of thumb?
>
> It's basically a "you just know" sort of things. For example, you
> don't want binaries world writable. You don't want stuff in /usr/doc/
> to be executable. In other words, just check to make sure your
> software is installed with reasonable permissions. Some time this is
> already done by make, but sometimes things are a little fuzzy too.
> Just look over your permissions and see if they make sense. If they
> don't, change them before packaging up everything.

And why are the permissions changed in build directories?
e.g.

(...)
cd gimp-$VERSION
chown -R root.root .
find . -perm 666 -exec chmod 644 {} \;
find . -perm 664 -exec chmod 644 {} \;
CFLAGS="$SLKCFLAGS" \
../configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var/lib \
--disable-static \
$ARCH-slackware-linux
(...)