Re: warn about conflicting skeleton-generated files

[Joel E. Denny]

On Sun, 10 Dec 2006, Hans Aberg wrote:

> Another problem, somehwat irritating, is that Biosn does not know how to parse
> the filepaths of the skeleton files. So if I write my own, and put it in the
> project in the home directory, I need to write things like:
>   bison --skeleton=../../../../Users/myself/Development/MLI/sources/
> Parser/my_lalr1.cc
> even if Bison is invoked form the last directory.

I think it would be useful if Bison were to recognize three forms of 
skeleton paths:

1. "/root/path"
2. "./cwd/path"
3. "path/relative/to/install"

It looks straight-forward to implement: don't prepend pkgdatadir for the 
first two forms.

Thoughts?