-
Notifications
You must be signed in to change notification settings - Fork 340
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
configure: Make rpmlint optional #5658
configure: Make rpmlint optional #5658
Conversation
configure.ac
Outdated
@@ -672,6 +689,7 @@ echo " | |||
Python: ${PYTHON} (${PYTHON_VERSION}) | |||
pylint: ${PYLINT} | |||
jslint: ${JSLINT} | |||
rpmlint: $enable_rpmlint |
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.
nit: shouldn't this follow the same pattern as the others, e.g. upper-case ${ENABLE_RPMLINT} ?
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.
Other than the nit the patch LGTM.
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.
PYLINT and JSLINT are shell variables in this case as well as enable_rpmlint. There is no common convention in IPA configure.ac regarding upper/low case(both exist). It doesn't matter for me. If you think the upper is more appropriate then I'll change it.
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.
That's true about inconsistency but most (I didn't check for all) of the optional/detected features use upper case. They universally use the ${} format.
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.
Thank you, pushed the 'upper' version.
Distributions may want to run comprehensive fastcheck or lint tasks, but rpmlint tool is mandatory for these targets while some platforms don't have it at all. With this change the rpmlint becomes optional for fastcheck, devcheck and lint make targets. Note: rpmlint option is disabled by default. To enable: ./configure --enable-rpmlint To explicitly disable: ./configure --disable-rpmlint Fixes: https://pagure.io/freeipa/issue/8768 Signed-off-by: Stanislav Levin <slev@altlinux.org>
Template the autoconf phase. Fixes: https://pagure.io/freeipa/issue/8768 Signed-off-by: Stanislav Levin <slev@altlinux.org>
24401fd
to
16e42e8
Compare
Maybe it's just that I have a tough time understanding how Azure actually works but the template script(s) aren't displayed in the output AFAICT so its difficult to verify that the right template is actually applied. For example the closest I can find to calling autogen.sh is: 2021-03-24T15:20:53.8776078Z [command]/usr/bin/bash --noprofile --norc /__w/_temp/0ed4b940-be80-48fa-be3a-705ef9e693a2.sh But what are the contents of /__w/_temp/0ed4b940-be80-48fa-be3a-705ef9e693a2.sh ? |
The content of
The traditional way is |
LGTM. |
@stanislavlevin could you please do
|
@abbra, thank you!
Sure, #5677 |
Distributions may want to run comprehensive fastcheck or lint tasks, but rpmlint tool is mandatory for these targets while some platforms don't have it at all.
With this change the rpmlint becomes optional for fastcheck, devcheck and lint make targets.
Note: rpmlint option is
disabled
by default.To enable:
./configure --enable-rpmlint
To explicitly disable:
./configure --disable-rpmlint
Fixes: https://pagure.io/freeipa/issue/8768