[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: warn about conflicting skeleton-generated files
From: |
Joel E. Denny |
Subject: |
Re: warn about conflicting skeleton-generated files |
Date: |
Thu, 14 Dec 2006 01:54:12 -0500 (EST) |
On Wed, 13 Dec 2006, Paul Eggert wrote:
> "Joel E. Denny" <address@hidden> writes:
>
> > I just remembered one place I've seen something like the above. These are
> > different:
> >
> > info --file=bison.info
> > info --file=./bison.info
>
> OK, that's enough precedent for me; you talked me into it.
Great.
If we do need --skeleton-path at some point, we can use `info -d' and
$INFOPATH as a precedent. For now, for simplicity, I think we can leave
that unimplemented.
I want to make sure we're clear on the algorithm. Unfortunately, using
`info info' I didn't find a clear explanation of `info --file'. However,
using `info bash' I did find some discussion of shell command execution.
I believe that discussion agrees with my experiences using both of those,
so I propose:
1. If the file name does not contain `/', prepend `pkgdatadir/'.
2. If it does, don't.
There's one caveat for that algorithm: if we one day decide that
pkgdatadir needs subdirectories of skeletons files where the same base
file name appears in more than one of them, I see no way to distinguish
among those files. However, I assume that we can always name Bison's
distributed skeletons uniquely.
A point of ambiguity just occurred to me. What are relative file names
relative to? For --skeleton, I think it's the current working directory.
For %skeleton, it seems like the grammar file directory, so that would
have to be prepended.
Does this all make sense?
> (My, you are a patient guy! :-)
Well, these discussions usually do prove useful.
- Re: warn about conflicting skeleton-generated files, (continued)
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/14
- Re: warn about conflicting skeleton-generated files,
Joel E. Denny <=
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/14
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/14
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/14
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/14
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13