romanz
clarify versioning scheme
i'm packaging trezor-agent and surrounding projects/dependencies like libagent for Guix.
this repo has multiple libs/apps in it, but obviously only one list of git tags.
the git tags seem to track libagent's versioning, but there's a version in agents/trezor/setup.py that is out of sync with the git tags/releases, even though its code is often changing (i guess due to libagent's API changing?).
maybe agents/trezor/setup.py should straight out inherit the version from libagent if possible?
@romanz it would help if you could clarify whether the version in agents/trezor/setup.py should be the same as libagent, i.e. the git tag. was it just a mistake that 'agents/trezor/setup.py' is not updated to the same version as libagent?
if it's just a mistake then i'd set the version of the Guix package accordingly, ignoring the version in agents/trezor/setup.py.
First of all - I am very sorry for the very delayed response!
My original idea was to version and release libagent and trezor-agent separately, but I think that you're right - and it would be easier to use a single version & tag for both of the projects.
@romanz have you considered creating separate repositories for hardware agent and libagent? They could be all be separate repositories under a Github Org. It would make packaging and versioning easier I imagine and avoid the confusion of all being under trezor-agent.
@doolio i think there's some architectural reason behind this. maybe trezor-agent is practically libagent plus some wrapping? but i may be way off here...
@romanz not sure whether you're still deciding, or it was just forgotten... so, it's a kind reminder that https://github.com/romanz/trezor-agent/blob/master/agents/trezor/setup.py still contains version='0.12.0' (and the same applies to the other agents).