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

VERSION_NUMBER fallback without eclipse? #16

Closed
merlight opened this issue Mar 6, 2015 · 1 comment
Closed

VERSION_NUMBER fallback without eclipse? #16

merlight opened this issue Mar 6, 2015 · 1 comment
Milestone

Comments

@merlight
Copy link
Contributor

merlight commented Mar 6, 2015

Two possible ways to make a freshly checked-out LAM load.

  1. Make the version token more unique and fallback to +inf if not defined. This relies on the non-existence of _G._LAM2_VERSION_NUMBER.
local MAJOR, MINOR = "LibAddonMenu-2.0", _LAM2_VERSION_NUMBER or math.huge
  1. Append some big number to the version token, and wrap it in quotes. This exploits the fact that LibStub searches the version string for a number, skipping any leading non-digits.
local MAJOR, MINOR = "LibAddonMenu-2.0", "VERSION_NUMBER_OR_999"
@sirinsidiator
Copy link
Owner

I was thinking about changing it to

local MAJOR, MINOR = "LibAddonMenu-2.0", 999

and update the build script to look for and replace that.

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

No branches or pull requests

2 participants