Attila Lendvai schreef op ma 11-04-2022 om 06:49 [+0000]: > these names are pretty much independent from each other > (modulo some conventions), and this is an issue for the importers. > more specifically the go importer, that currently needs scheme variable > names to refer to the identified dependencies, while it can only look up > the package objects. these objects know nothing about the scheme > variables they are stored in.
Use package-definition-location. From the file name, it should be possibly to derive a module name. The sexp at this location can also be read -- the sexp includes the surrounding (define-public foo ...), so the variable name can be extracted. Greetings, Maxime.
signature.asc
Description: This is a digitally signed message part
