Top-level module versioning for Lola modules

[trevor-vaughan]

Hi Folks,

I've just started using lola and it's been pretty good for what I want to achieve.

I just ran into something that made me wonder if I was just missing a use case. I'm creating and testing some local modules that have multiple components internally. I figured I'd be able to drop a version file in somewhere but haven't been able to actually determine where this is.

A dumpster dive through the code seems to indicate that the marketplace will have versions but there doesn't seem to be support for standalone versions in modules.

Is this something that the community would like to have or is it a "marketplace is the truth" scenario?

Taking the dnf reference from the README, I would expect something like a lola.yml that specifies all of the necessary metadata and is used to generate the final package (which could be rolled up in an rpm if you really want to go for it).

[trevor-vaughan]

A lola.yml would also be nice for pinning a name to the project when installing from a repo.