[Slackbuilds-users] Updates - 20170715.1 ownership

[Willy Sudiarto Raharjo]

> to clarify: one of the first things we do in our templates, just after
> uncompressing the upstream tarball, is executing this block
> 
> chown -R root:root .
> find -L . \
>  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>   -o -perm 511 \) -exec chmod 755 {} \; -o \
>  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
> 
> after running this ownership and permissions are fine in the sources
> directory, so it's safe to execute cp -a from there (I think Willy
> meant that).

yes, you are safe to use cp -a if you take something from the directory
created after you extract the tarball/zip files (eg. documentations such
as README, AUTHORS, etc).

the problem lies when you take a file outside the tarball which normally
taken from the same directory as the SlackBuild script (eg, README.SBo,
README.Slackware, etc) since it will not have the same owner as the
files extracted from upstream tarball, so we need to use cp or make sure
the owner is root just before macking the package using makepkg.

I hope that clarify my original intention


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170715/65147235/attachment.asc>