Re: [Chicken-hackers] [PATCH] Use name from egg file when installing types and inline files

[Kooda]

On Sat, 9 Sep 2017 16:14:44 +1200 Evan Hanson <address@hidden>
wrote:
> Please ignore this patch, Kooda has pointed out that the current
> behaviour makes more sense.
> 

Well, actually, I’m not sure what makes more sense. I think it’s
strange that types and inline files are relative paths in the install
script while every other file is an absolute path.

The other thing I find strange, is that the doc says that the
(types-file) and (inline-file) declarations “Specifies that a
"type-database" file should be generated and installed…”, but currently
they don’t produce any code to generate them.

All is left to do so is passing `-ot` and `-oi` to csc, through
(link-options) for example, and thus the .egg file writer can’t put an
absolute path for those options because there is nothing in the .egg
file specification to do so.

So indeed the current behaviour makes more sense but I still think it’s
wrong.

Also, what’s the use of the file name overwrite for these two options?
I would think the component name is always the right name.

In any case, I think we need a way to specify whether the types/inline
file should be generated or taken from a manually written file in the
egg source directory.