Skip to content

use omego - #266

Closed
jburel wants to merge 1 commit into
ome:developfrom
jburel:omego
Closed

use omego#266
jburel wants to merge 1 commit into
ome:developfrom
jburel:omego

Conversation

@jburel

@jburel jburel commented Jul 4, 2022

Copy link
Copy Markdown
Member

To avoid update of the documentation when new version will be release e.g. 5.7.0
the command will install the latest version in the 5 series

@dominikl

dominikl commented Jul 6, 2022

Copy link
Copy Markdown
Member

Looks good to me. Tested it only with Debian10, but as it's all the same for the other distros, that should be enough, isn't it?

@jburel

jburel commented Jul 6, 2022

Copy link
Copy Markdown
Member Author

As discussed in ome/openmicroscopy#6330, the main question is if we want to expose omego or not in the installation steps

@dominikl the installation is tested via GHA

@joshmoore

Copy link
Copy Markdown
Member

For that diff, @jburel, it might not be warranted. Are there other locations you have in mind for using omego?

@jburel

jburel commented Jul 11, 2022

Copy link
Copy Markdown
Member Author

Not really, But if we have ome/openmicroscopy#6318 in without any build number
I could easily:

  • find the latest version from GitHub
  • build the URL from GitHub.

i.e. no usage of omego
I was planning initially to use it ome/omero-documentation#2261 but I am happy with the alternative solution.

@jburel

jburel commented Jul 26, 2022

Copy link
Copy Markdown
Member Author

Closing this PR. I don't think I will be using omego. With ome/openmicroscopy#6318 in, build number will not be present so it will be possible to build a URL.

@jburel jburel closed this Jul 26, 2022
@jburel
jburel deleted the omego branch September 7, 2023 08:08
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