Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow doesn't document ONNV_BUILDNUM #22

Open
trisk opened this issue Nov 21, 2015 · 2 comments
Open

Workflow doesn't document ONNV_BUILDNUM #22

trisk opened this issue Nov 21, 2015 · 2 comments

Comments

@trisk
Copy link
Member

trisk commented Nov 21, 2015

Current doc doesn't mention that ONNV_BUILDNUM may need incrementing in most or all install target environments.

@rmustacc
Copy link
Contributor

Can you summarize the current rules one should use in determining how to set it, or ultimately, am I better off just doing a per-distro section here?

@trisk
Copy link
Member Author

trisk commented Nov 21, 2015

It's technically only relevant to distros that use the pkg(5) metadata for upgrades. My previous suggestion on the wiki was:
"Run:

pkg info osnet-incorporation | grep Branch:

If you see, for example, "Branch: 0.151.1", you must choose a number greater than the part after the leading "0.". For example, add
export ONNV_BUILDNUM=152
to the illumos.sh script."

I never determined if ONNV_BUILDNUM could have decimals as well.

A large sequence of digits such as YYYYMMDD is also likely to be fine for all existing distros and probably more useful, though this may bring up the gate versioning arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants