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

How do I select a specific package version #14

Open
flaviojs opened this issue May 2, 2024 · 5 comments
Open

How do I select a specific package version #14

flaviojs opened this issue May 2, 2024 · 5 comments

Comments

@flaviojs
Copy link

flaviojs commented May 2, 2024

I am trying to build with cygwin (no mingw or msys2) in a windows-latest github runner.
In an attempt to fix build issues I want to try an older version of gcc but don't know how to select the package version.

Can you give me an example of how it is done and update the docs?
If the feature is not available, please add it.

@jon-turney
Copy link
Member

Good question. Unfortunately, because Cygwin uses a rolling distribution, there are no good answers.

Setup accepts package=version-release constraints in the package list fed to it, and those probably make their way through this action unchanged, so you could probably just put those in the packages parameter to this action.

But that's unreliable, because it won't work after the required version has been expired from the Cygwin package repository.

The other method would be to pick a historical Cygwin snapshot from the Cygwin Time Machine, which has the version(s) you want, and specify the appropriate circa (timestamp) URL as the site parameter to this action.

There's definitely a need for better documentation on this point, here, but also on the Cygwin website itself...

@flaviojs
Copy link
Author

flaviojs commented May 3, 2024

Thanks for the info. =)

I tried with gcc-core=7.4.0-1 (last version with working ada) but still got the latest version installed.
With gcc-core==7.4.0-1 it said version =7.4.0-1 not found so maybe setup has a bug where it parses the wanted version but ignores it in practice.

@flaviojs
Copy link
Author

flaviojs commented May 4, 2024

After fixing my build issues I dedicated some time analyzing the setup.exe source:

  1. ChooserPage::applyCommandLinePackageSelection() ignores the install wanted_version when UpgradeAlsoOption is true.
  2. Command line option '-g' sets UpgradeAlsoOption to true.
  3. running the same command-line commands as this github actions show the same bad behavior.
  4. removing the -g option installs the requested gcc-core version (7.4.0-1).

@Laguna1989
Copy link

Also interested in this if it is fixed yet 👀

@kmilos
Copy link

kmilos commented Oct 7, 2024

Same here, would like gcc 13 from test...

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

4 participants