Retiring WITH_INSTALL_AS_USER

[Warner Losh]

On Oct 23, 2014, at 9:58 AM, Simon J. Gerraty <sjg at juniper.net> wrote:

> Warner Losh <imp at bsdimp.com> wrote:
>> If it is in the tree, it needs to work. 
> 
> 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.

Buildworld it is fine. installworld is where it breaks. In a lot of places.

> 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’d 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. 
> 
> Sounds ok. 
> 
> Hmm etc/Makefile looks like it lost the ability to run mtree safely 
> 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?

That’s a good question. With NO_ROOT you postpone the unknown users until makefs time. There’s both pros and cons to that...

Warner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20141025/96e0ff4d/attachment.sig>