Date: Sun, 10 Dec 2000 13:15:34 -0800 From: Marcel Moolenaar <marcel@cup.hp.com> To: current@FreeBSD.org Subject: Re: using mtree in our builds [was: Re: Bootstrapping issues with groff(1)] Message-ID: <3A33F276.FC7FDFE@cup.hp.com> References: <20001208181908.A12716@sunbay.com> <3A319650.90FE8EAE@cup.hp.com> <20001209154901.B78374@sunbay.com> <3A32996C.1BE57FCE@cup.hp.com> <20001209192429.A32252@dragon.nuxi.com> <3A32FFB2.BCCC5140@cup.hp.com> <20001210115049.H80274@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > > On Sat, Dec 09, 2000 at 07:59:46PM -0800, Marcel Moolenaar wrote: > > > The only thing you don't like about mtree is it changing ownership + > > > modes, right? > > > > Not only that. Using mtree(1) creates busloads of unnecessary > > directories. > > But they're harmless. While I agree it is clutter, having to duplicate > its work in the Makefile's with lists of dirs to create just seems like a > duplication and waste of effort; If the list is short (as it is now), there's no real problem, but if there's a real bootstrapping issue with groff(1) and we need to add 10+ directories, then it will become a more serious issue and I think that a better solution is called for in that case. > and even an little NIH as mtree is > rather ingrained in BSD. NIH has nothing to do with it. To me it seems that mtree(1) is designed for a different purpose. Yes, it so happens that mtree can create directories, but that's not the root purpose of the tool. And yet, that's the only reason we'll use mtree(1) in the build (at all?). Adding features to mtree to have it better function in our builds only adds to the bootstrapping overhead, and all we really want to reuse is the directory structure information in our BSD.*.dist files. If the effort to write a small script is of the same order as patching mtree, then I prefer the small script... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A33F276.FC7FDFE>