Date: Tue, 13 Dec 2016 23:01:13 +0100 From: Matthias Andree <matthias.andree@gmx.de> To: null <freebsd-ports@freebsd.org> Subject: Re: No port should need root for make fetch Message-ID: <96f44b17-b5a3-d24e-dee4-935d55a70019@gmx.de> In-Reply-To: <201612132135.uBDLZPVp017655@fire.js.berklix.net> References: <201612132135.uBDLZPVp017655@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 13.12.2016 um 22:35 schrieb Julian H. Stacey:
>
>> How is that a problem of "some" ports? All ports require root for "mak=
e
>> fetch"
> No they dont.
Given that, then "none do".=20
I'll do what what you omitted in your blind rage, I've dug the important
detail up for you, which was the first guess:
$ grep _DEPENDS Makefile /dev/null
/usr/ports/databases/mysql-q4m/Makefile:FETCH_DEPENDS+=3D =20
${NONEXISTENT}:${_MYSQL_SERVER}:build
This doesn't say "give me root". It needs to be able to build the
requisite port.
Obviously the fix is to make sure that if you want to fetch as
unprivileged user, that you can also *build*.
I assume that if you want *fetch* as unprivileged user, that you also
want to *build* as unprivileged user, so I'd take that for granted, but
it's not the case on your system.
On my system, which has a WRKDIRPREFIX that I am permitted to write to
with the unprivileged user account doing the builds, "make fetch" for
mysql-q4m passes without a hitch.
> Thanks for the well intentioned & good advice Matthias,
> But some few ports are truly Badly Behaved with make fetch.
Can you cite chapter and verse of the rule that makes such a port "truly
Badly Behaved", for reference in this list's archives?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96f44b17-b5a3-d24e-dee4-935d55a70019>