NEED_ROOT
From my reading it appears that one of the goals of STAGE is to allow users
to build and install ports under their UID. Are the perms in /usr/ports
changing?
In testing the port that I'm working on, I find that I do not have rights
to write to /usr/ports/distfiles and I do not have rights to write to
${WORKDIR}. That pretty much precludes building the port unless your root.
No surprise there since the files in /usr/ports are owned by root:wheel.
So are the perms going to change? Is port building going to run setuid?
Or is this a vaporware?
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: NEED_ROOT
On 2013-Oct-04 16:45:34 -0500, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
From my reading it appears that one of the goals of STAGE is to allow users
to build and install ports under their UID. Are the perms in /usr/ports
changing?
I hope not. There's nothing wrong with the current permissions.
In testing the port that I'm working on, I find that I do not have rights
to write to /usr/ports/distfiles and I do not have rights to write to
${WORKDIR}. That pretty much precludes building the port unless your root.
No surprise there since the files in /usr/ports are owned by root:wheel.
I've built ports as non-root, with a read-mostly /usr/ports for many
years. All you need to do is override the defaults:
WRKDIRPREFIX=/tmp
PACKAGES=/where/you/want/packages
DISTDIR=/where/you/want/distfiles
Alternatively, I chmod 1777 /usr/ports/distfiles to allow a common
ports tree to be shared amongst multiple systems. And you can also
use symlinks.
--
Peter Jeremy
pgpBxCwC_XcAn.pgp
Description: PGP signature
Re: NEED_ROOT
On 10/4/2013 11:45 PM, Paul Schmehl wrote:
From my reading it appears that one of the goals of STAGE is to allow
users
to build and install ports under their UID. Are the perms in
/usr/ports changing?
In testing the port that I'm working on, I find that I do not have
rights to write to /usr/ports/distfiles and I do not have rights to
write to ${WORKDIR}. That pretty much precludes building the port
unless your root. No surprise there since the files in /usr/ports are
owned by root:wheel.
So are the perms going to change? Is port building going to run
setuid? Or is this a vaporware?
Well... set WRKDIRPREFIX and DISTDIR to point somewhere writable by your
user.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: NEED_ROOT
On Fri, Oct 4, 2013 at 2:45 PM, Paul Schmehl pschmehl_li...@tx.rr.comwrote: From my reading it appears that one of the goals of STAGE is to allow users to build and install ports under their UID. Are the perms in /usr/ports changing? You've always been able to build ports as non-root, so long as you set WRKDIRPREFIX and DISTDIR to something you can write to. You've never been able to install ports as non-root. What the STAGE support stuff does is allow you to build _packages_ as non-root. Previously, to build a package, you first had to install the port (as root), then build the package (as non-root), then uninstall the port (as root). Now, you build the port (as non-root), install into the staging directory (as non-root), and make the package based on that (as non-root). IOW, root is only needed to install the package onto the destination system. It's not needed on the build system. -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
