Re: [Bug-tar] Option --exclude-ignore behaves unexpectedly

[Chris Marusich]

Chris Marusich <address@hidden> writes:

> Hi,
>
> I've noticed that the --exclude-ignore option to tar behaves in a way I
> didn't expect.  I've attached a script you can run in a clean temporary
> directory to demonstrate this.  Here's what I see when I copy the script
> into an empty directory, cd into that directory, and run it:
>
> Before:
> a:
> b  exclusions
>
> a/b:
> c
>
> Tarball contents:
> a/
> a/exclusions
> a/b/
>
>
> My understanding is that the file specified by --exclude-ignore only
> applies to the directory it's in, so I expected a result like the
> following:
>
> Tarball contents:
> a/
> a/exclusions
> a/b/
> a/b/c
>
>
> The behavior I expected seems to be in line with the manual, which says
> the following ((tar) Option Summary):
>
> '--exclude-ignore=FILE'
>      Before dumping a directory, 'tar' checks if it contains FILE.  If
>      so, exclusion patterns are read from this file.  The patterns
>      affect only the directory itself.  *Note exclude::.
>
> However, that isn't the behavior I've observed.  Instead, it looks like
> tar has excluded c, even though the file specified by --exclude-ignore
> should have only applied to directory a, not to its child directory b.
>
> Is the behavior I've observed intended?  Based on what the manual says,
> I suspect it isn't.

Is this behavior intended?  If it isn't intended, then I'm happy to
investigate to the best of my ability, but if the behavior is in fact
intended, then there is no point in investigating further.

Thank you,

-- 
Chris

signature.asc
Description: PGP signature