Skip to content

Ability to set arbitrary version of binary when "plasmactl build -p" #22

@davidferlay

Description

@davidferlay

Current

➜  launchrctl build -p github.com/launchrctl/launchr@latest -n xxx -o xxx       
Starting building xxx
Creating project files and fetching dependencies
(...)
Building xxx
Build complete: xxx

➜ ./xxx --version
xxx version v0.5.2 linux/amd64
Built with launchrctl version v0.5.2 linux/amd64
  • Version of built binary inherit the version of launchrctl which was used to build it
  • There is no option to define a specific version for built binary

Expected

  • There could be an option to define a specific version for built binary
  • So that using build command with --version v0.66.0 would render as
➜ ./xxx --version
xxx version v0.66.0 linux/amd64   <--------------------
Built with launchrctl version v0.5.2 linux/amd64
  • That particularly makes sense when binary is build to include multiple plugins, where each plugin -launchrctl included- has it's own version
    • It makes sense that built binary follow it's own versioning

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions