jocelyn
commented
6 years ago An iron package can contain one or many Eiffel configuration files (ecf). Even if the package.iron file can list the projects (... the ecf locations) when installing an iron package, the installer looks at all the .ecf to see which libraries are included, and then install the associated iron package(s).
I guess what you suggest is to care only about the ecf declared in the package.iron . Am I right?
Do you see any concrete cases where scanning for ecf file in the package may be an issue? (by the way, this is not done randomly)
What does this error message mean?
I have added a local repository (empty directory), created a symlink to the Gobo directory, added a package.iron to Gobo, and tried to install this package. Probably totally not the way you create repositories, but I'm just playing with this tool until I understand what it does, and hopefully improve any error messages a lay person may see.
Somehow it searches for all .ecf files in this directory (why?). Then complains it cannot install any of them. What's the idea behind this?
Note the package explicitly lists several projects.
I think randomly scanning a project for .ecf files is not a good idea. This should be dropped.