Closed joaquimrcarvalho closed 10 months ago
Note that a given kleio server can have a kleio-home mapped to a parent directory of server sources directory, as it happens in mhk-home layouts.
In those cases the above patterns would apply to KLEIO_HOME/sources/REPOSITORY/sources/SUBPATH/file.cli
Fixed in e4baeb001a531542363f56c033ee960ee65f5bfd
Rationale
It is important that diferent source collections can use different stru definitions.
One of the current problems is that for every new source format the shared
gacto2.str
has to be changed.By allowing the stru file to be stored close to the sources directory it is possible to have different
stru
in usage.implementation
The standard source repository has a
sources
directory at the same level of astructures
directory.So for a given source file to be translated with path
sources/SUBPATH/file.cli
the default stru would be, in order:structures/SUBPATH/file.str
structures/SUBPATH2/gacto2.str
whereSUBPATH2
is a parent path of SUBPATHstructures/DIRNAME.str
where DIRNAME, is the name of a dir in SUBPATHstructures/gacto2.str
can be replaced bysources.str
for clarity in all patterns.This allows for a source repository to have formats specific to a single file, a sub directory of files or to all the sources in the repository:
structures/baptisms/baptism-index.str
format specific forsources/baptisms/baptism-index.cli
structures/baptisms/gacto2.str
orstructures/baptisms/sources.str
for all sources insidesources/baptisms
and sub directoriesstructures/baptisms.str
for all sources insources/baptisms
(not sure about this one, the advantage is to manage more easily different structure files with different names)structures/gacto2.str
orstructures/sources.str
default str for all sources.