Closed mgomersbach closed 4 years ago
Sorry for the delay @mgomersbach. We don't have a suitable test environment for Gentoo and it doesn't seem easy to achieve, either.
So this continues from #156. I understand the need for the changes (i.e. version
) but I'm not quite sure what the changes achieve.
version
but what exactly is uses
?use
requisite?'[php_targets_php' + useversion + ']'
?Sorry for the delay @mgomersbach. We don't have a suitable test environment for Gentoo and it doesn't seem easy to achieve, either.
I know, Gentoo is not high profile, so any support at all is greatly appreciated.
So this continues from #156. I understand the need for the changes (i.e.
version
) but I'm not quite sure what the changes achieve.* Of course, it shouldn't be referring to `version` but what exactly is `uses`?
"uses" is from the ebuildpkg module.
Most features listed here come from compiles the package "dev-lang/php" with a useflag. And external ones have useflags with versions in it. A dash between numbers in the useflag (like: [php_targets_php7-3] ) generates a error like in the error report. Somewhere it gets interpreted as regex syntax, and was not able to generate the right escape sequence around it.
Merged, thanks for the contribution @mgomersbach.
I know, Gentoo is not high profile, so any support at all is greatly appreciated.
Not a problem, this PR has stimulated some discussion about how to get tests running on Gentoo. It would be great if you could bring any of your suggestions, such as how to install a specific version of Salt:
"uses" is from the ebuildpkg module.
Great, that's exactly what I needed to know. At least we have some reference to that now in this discussion.
:tada: This PR is included in version 1.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
When using version inside useflag, the sls_block macro with ebuildpkg regex result in a range error. Replacing the version argument with uses seem to work as escapes don't really work there.
Pillar / config required to test the proposed changes
Current master branch has non working targets
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context
Before it got moved from ng namespace, I created a lot of this mess.