-
Notifications
You must be signed in to change notification settings - Fork 33
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
u3d/list: display full revision number (prepares for #274) #280
Conversation
@@ -163,6 +167,39 @@ def plist | |||
end | |||
end | |||
|
|||
class LinuxInstallationHelper | |||
STRINGS_FULL_VERSION_MATCHER = /^[0-9\.abfp]+_[0-9a-f]{12}/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here I would have to check if we get weird values, e.g. with some of the versions that had weird build numbers.
It works nicely on Windows :)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nitpicking regarding the installation helpers. Feel free to merge without though
@@ -176,6 +213,10 @@ def version | |||
version | |||
end | |||
|
|||
def build_number | |||
@build_number ||= LinuxInstallationHelper.new.find_build_number(root_path) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could make the find_build_number
a class method rather than an instance? It would make a bit more sense to me. Especially given the fact that the Helper doesn't carry any sort of data so all of its current methods could be moved to self?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to avoid class methods! I don't find them particularly elegant from an API point of view. Thoses classes are meant internal though, not part of the public API in my mind.
Pull Request Checklist
bundle exec rspec
to make sure that my PR didn't break any testbundle exec rubocop
to make sure that my PR is inline with our code stylePull Request Description
Tested on Linux/Windows/Mac on the computers I had access to, would need slightly more testing to make sure Unity doesn't do weird things with special builds. So adding the feature as part of
list
to test it a bit more.We need to work a bit more on the overall feature set to see how to solve #274
Mac:
Linux:
Windows:
Meh... believe me it worked.