Source tree has many empty directories?
Warner Losh
imp at bsdimp.com
Tue Sep 10 19:48:30 UTC 2019
On Tue, Sep 10, 2019, 1:43 PM Ian Lepore <ian at freebsd.org> wrote:
> On Tue, 2019-09-10 at 21:41 +0200, Dimitry Andric wrote:
> > On 10 Sep 2019, at 20:14, Ian Lepore <ian at FreeBSD.org> wrote:
> > >
> > > On Tue, 2019-09-10 at 11:01 -0600, Warner Losh wrote:
> > > > However, please do *NOT* remove the sys/*/compile directories.
> > > >
> > > > Warner
> > >
> > > Uhhh... that's interesting. I just nuked one of those on my system
> > > yesterday, because it had been hanging around since 2013 and I had no
> > > idea what was -- I just assumed the build machinery created it because
> > > I had accidentally done a make in a wrong directory once.
> > >
> > > So what are those directories about? I'm not used to seeing mystery
> > > directories appear inside a source tree.
> >
> > There's not much mystery to be found. Subversion does not warn you when
> you
> > remove the last files from a directory, and it also does not
> automatically
> > remove such empty directories, like Git. Hence, those directories tend
> to
> > stick around, because every simply forgets about them.
> >
> > With regards to those empty directories under contrib/llvm, those were
> actually
> > imported from upstream. But since the llvm project will switch to Git
> soon,
> > this problem will automagically disappear. :-)
> >
> > -Dimitry
> >
>
> I was referring specifically to the sys/*/compile directories Warner
> mentioned.
>
They are for old school builds. Config(8) doesn't create them, so we have
them in the tree. Because svn does this, we deleted the keep me files after
the cut over.
Warner
>
More information about the freebsd-current
mailing list