Date: Thu, 28 Jun 2018 13:43:41 -0400 From: Joseph Ward <jbwlists@hilltopgroup.com> To: Mathieu Arnold <mat@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: Any way to prevent do-extract chmod and chown? Message-ID: <dca25697-9a4f-deb7-f36d-7753d0fd27ae@hilltopgroup.com> In-Reply-To: <20180628082738.uv3bs6jmrrp52h5m@atuin.in.mat.cc> References: <dbfc8dbc-547c-74d9-e2dc-3cb3367293e1@hilltopgroup.com> <20180628082738.uv3bs6jmrrp52h5m@atuin.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you. I found that to be the case; even though changing the
"do-extract" target successfully staged the files and directories with
the original permissions, pkg create seems to strip them out again
without the pkg-plist additions.
Are you aware of an easy/already existing command to create the
pkg-plist with the user/group/permissions items for each file, or is
that a script I'm going to have to write manually? I'm currently using
the makeplist target as there are no subsitutions or anything else that
would screw up the default scenario.
Thanks,
Joseph
On 06/28/2018 04:27, Mathieu Arnold wrote:
> On Wed, Jun 27, 2018 at 07:06:44PM -0400, Joseph Ward wrote:
>> Hi everyone,
>>
>> I'm creating some internal-only ports and I'm trying to maintain the
>> permissions and owners of the files present in the distfile.tar.gz when
>> they get packaged up for install.
>>
>> When I "make extract", the "do-extract" target is performing a chmod and
>> chown on everything, as seen from the following excerpt from the
>> bsd.port.mk file:
>>
>>
>> .if !target(do-extract)
>> do-extract: ${EXTRACT_WRKDIR}
>> @for file in ${EXTRACT_ONLY}; do \
>> if ! (cd ${EXTRACT_WRKDIR} && ${EXTRACT_CMD}
>> ${EXTRACT_BEFORE_ARGS} ${_DISTDIR}/$$file ${EXTRACT_AFTER_ARGS});\
>> then \
>> exit 1; \
>> fi; \
>> done
>> @if [ ${UID} = 0 ]; then \
>> ${CHMOD} -R ug-s ${WRKDIR}; \
>> ${CHOWN} -R 0:0 ${WRKDIR}; \
>> fi
>> .endif
>>
>>
>> Short of commenting those lines out (which I really don't want to do
>> because I have 0 idea why it's there or what I'd break with other ports)
>> is there any way at all to maintain the ownership of the files?
> Building ports as root is a rare thing these days, most build tools
> build everything as a regular user (most of the time, nobody) so
> ownership of files in distribution files is not retained anyway.
>
> To set user/group/mode ownership in the resulting packages, you need to use
> the @user, @group and @mode keywords in the pkg-plist file. (or the @
> keyword if one file needs a specific user/group/mode.) See:
>
> https://www.freebsd.org/doc/en/books/porters-handbook/plist-keywords.html
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dca25697-9a4f-deb7-f36d-7753d0fd27ae>