Date: Thu, 23 Oct 2014 07:58:55 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Arch <freebsd-arch@freebsd.org> Subject: Re: Retiring WITH_INSTALL_AS_USER Message-ID: <9250.1414076335@chaos> In-Reply-To: <E40CAE9C-0C6B-4D7C-879E-53926D0A775E@bsdimp.com> References: <96C0B2BE-0621-4162-BBB7-7D34AEAB5FD0@gmail.com> <21044.1414038558@chaos> <E40CAE9C-0C6B-4D7C-879E-53926D0A775E@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh <imp@bsdimp.com> wrote: > If it is in the tree, it needs to work.=20 No argument there. > It is broken in about a dozen places > now. Perhaps not the ones that you use. Hmm I have it permanently set in a projects/bmake tree that builds buildworld etc fine (while producing meta files) - though its been a month or two since last sync. Internally we have it set in head trees too. I don't doubt there's something lacking - just haven't noticed, sorry. > Makefile.inc1 is the only place it is documented right now. NO_ROOT > creates a METADATA file for the attributes of the file and does simple > copies instead. This lets you build entirely as an unpriv=E2=80=99d user,= but > still use makefs to get a filesystem with the proper attributes. In > many ways it is what you want, and you could get what you want by > specifying /dev/null for that METADATA if it were more tightly > coupled.=20 Sounds ok.=20 Hmm etc/Makefile looks like it lost the ability to run mtree safely=20 in a cross-build env? The MTREE_FILTER stuff ensures that mtree doesn't choke on unknown users and such. How is that handled now?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9250.1414076335>