Skip to content

Conversation

@DarwinJS
Copy link
Contributor

This version detects the currently available version on github.
Details:

  • It uses sed to parse json - so hopefully can be deployed universally without any runtime installs
  • self-documenting comment on how to pull directly from the web
  • only tested on ubuntu and centos - could use testing on other supported platforms.
  • the sed string might be able to be cleaned up with someone who knows sed better than I (like everyone)

Autodetects current release from github using pure bash (sed)
@msftclas
Copy link

@DarwinJS,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


case "$VERSION_ID" in
14.04)
package=powershell_6.0.0-alpha.18-1ubuntu1.14.04.1_amd64.deb
Copy link
Member

Choose a reason for hiding this comment

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

Where installation via package manager is available, can we switch to using that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We're on the same page! I am thinking that when I add the repos I should make the initial install request specifying the version as the version that comes down in the version tag on git. That way if there happens to a sync issue where a newer than the latest "official" release is hanging around, this code only installs the official release tagged as latest on git?

Copy link
Member

Choose a reason for hiding this comment

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

I think it should just install the latest version from the repo. Eventually, we will have a non-pre-release version, and I think then we have a decision to make, but currently, if it's in the repo, it's ready.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Suits me - easier to code ;)

Copy link
Member

@TravisEz13 TravisEz13 left a comment

Choose a reason for hiding this comment

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

The build is failing. It should be fixed

@DarwinJS
Copy link
Contributor Author

Another question - is the "Centos" release really only good for Centos - or also Rhel? Right now the logic limits it to Centos.

@TravisEz13
Copy link
Member

CentOS, my understanding is that it should work on the same version of Rhel.

@DarwinJS
Copy link
Contributor Author

I've made a proposal here: #3547

@DarwinJS
Copy link
Contributor Author

@TravisEz13 - is every .sh that is uploaded tested against every distro - or is there a way to specify which ones run on which test targets?

@TravisEz13
Copy link
Member

Which .sh file are we talking about? I doubt there is a way to specify which distro it is tested on. that would have to be written.

@TravisEz13
Copy link
Member

What do you want to do with this PR?

@DarwinJS
Copy link
Contributor Author

I would like to merge it, however, I don't have a way to test the OSX code (that now uses brew.)

Would be especially helpful to test on a pristine system.

@TravisEz13
Copy link
Member

If you fix the merge conflicts, I can probably help you test it.

@DarwinJS
Copy link
Contributor Author

@TravisEz13 - this is superceded by #3608

@TravisEz13
Copy link
Member

Closing because this is superseded

@TravisEz13 TravisEz13 closed this Jul 21, 2017
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

Successfully merging this pull request may close these issues.

3 participants