freebsd-update and lib32

[Dimitry Andric]

On 30 Jan 2015, at 18:20, Shane Ambler <FreeBSD at ShaneWare.Biz> wrote:
> 
> On 31/01/2015 00:20, Marko Cupać wrote:
...
>> I have noticed that, after initial install of FreeBSD 10.1-RELEASE
>> without lib32 selected, /usr/lib32 folder is created nevertheless,
>> containing 3 empty dirs: dtrace, i18n and private. However, running
>> freebsd-update on such system pulls a bunch of files into /usr/lib32
>> and its subdirs while updating to FreeBSD 10.1-RELEASE-p5.
> 
> Doing a buildworld WITHOUT_LIB32 still creates these dirs. I reported
> it a while back but it is still on someones todo list. Not sure if that
> is also related to freebsd-update or is the cause of it triggering the
> lib32 install.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165175

Yes, this is because installworld creates all the directories in the
destination with mtree(8), using the specification files in
/usr/src/etc/mtree.  However, mtree does not support conditional
creation, for example to only create /usr/lib32 when you have that
option enabled.

I'm not sure if anybody is working on this, as it is not a very big
issue: empty directories do not influence the working of your system,
and they cost almost no disk space.  But it is rather tricky to solve,
at least in an elegant way.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150130/33d3797e/attachment.sig>