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

Note that 9999.99.0.0 will not allow user to go back to OI-provided p… #41

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pyhalov
Copy link
Contributor

@pyhalov pyhalov commented Apr 15, 2019

…ackages

@bdha bdha requested a review from jclulow April 15, 2019 12:20
@@ -191,6 +191,9 @@ can find out the current branch version with `pkg info`:
$ pkg info osnet-incorporation | grep Branch:
Branch: 2018.0.0.18230
```
If you want to be able to update your system to illumos-gate packages, provided
by OpenIndiana, it's adviced to increment only last number of the branch
version.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we make this paragraph say:

The example value of 9999.99.0.0 will effectively guarantee your packages will always be preferred forever. If you want to be able to return to using official OpenIndiana packages in the future, you should instead use a PKGVERS_BRANCH value that only increments the last number; e.g., if pkg info tells you your current branch is 2018.0.0.18230, you would use 2018.0.0.18231.

As markdown source, that would be:

The example value of `9999.99.0.0` will effectively guarantee your packages 
will _always_ be preferred forever.  If you want to be able to return to using
official OpenIndiana packages in the future, you should instead use a
`PKGVERS_BRANCH` value that only increments the last number; e.g., if `pkg
info` tells you your current branch is `2018.0.0.18230`, you would use
`2018.0.0.18231`.

@pyhalov
Copy link
Contributor Author

pyhalov commented Aug 9, 2019

@jclulow ping

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

Successfully merging this pull request may close these issues.

None yet

2 participants