oxidecomputer / oxidecomputer/helios
Would like way to have wsdiff friendly VERSION string
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 481
- Forks
- 21
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 2
Description
I realize there's a lot of ways to slice and dice the wsdiff version string. For development builds I find the generic use of VERSION being set to something based on the path. So for example, I often have whether with smartos in the past or something else, basically a single instance of helios / smartos-live / illumos-gate for each active thing. They usually end up in something like /ws/rm/XXX or a subdir of ~/. The main reason for this is identification. I guess you could in theory always use meaningful BE names or related, but I just find it easier for dev to be that way personally.
I totally realize this is a everyone's workflow is different. However, the one thing I know is that including the git sha won't work for wsdiff because everything will be different. I'm not sure what makes sense for individual development builds or others, but that's something to think about.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the current VERSION string is generated for development builds and how wsdiff compares it. Done requires an agreed VERSION scheme that identifies development instances while remaining compatible with wsdiff; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100