find_list_entry.c and "FNM_LEADING_DIR"?

[Robert P. J. Day]

On Mon, 17 Apr 2006, Glenn L. McGrath wrote:

> On Sun, 16 Apr 2006 11:21:56 -0400 (EDT)
> "Robert P. J. Day" <rpjday at mindspring.com> wrote:
>
> >
> >   so what's the consensus on adding that option to the call to
> > fnmatch() in that file?  that's the only thing that's stopping me from
> > tossing a separately-compiled tar executable and being able to use the
> > BB tar applet.
>
> It would surprise me if it didnt break something, but if you want to
> be responsable for fixing the breakage then fine by me.
>
> I think all the apps it effects should be tested first.
>
> If it really is causing you problems then you could make the change
> locally in your tree, give the changes a field test.

i tested it locally to the extent that i pounded on it pretty hard
through "tar" to make sure all of the behaviour was sane.  i do know
that it's technically a GNU extension and, if there's another way to
get the same effect, i'd be happy with that as well.

recall, i just want BB tar to emulate this behaviour of GNU tar:

  $ tar --exclude=./dir -xvf (tarball)

which will exclude "./dir" recursively.  if there's a simpler way to
recursively exclude a directory on extraction, that would be fine.

rday

p.s.  perhaps i should be asking a simpler question -- what are the
expected semantics of tar's "--exclude" option?  am i expecting too
much of it?  where is it defined what it *should* do?