configure fails when either pylint or jsl are not available. Both components are only relevant for developers. Default settings for configure should be tailored towards ordinary users. A developer will
$ sudo dnf remove pylint jsl $ autoreconf -ifv $ ./configure ... checking for Pylint... /usr/bin/python: No module named pylint configure: error: cannot find pylint for /usr/bin/python $ sudo dnf install -y pylint $ ./configure checking for Pylint... yes checking for jsl... no configure: error: cannot find JS lint
Also the options to disable linters are confusing:
$ ./configure --disable-pylint --without-jslint
One component uses --disable, the other --without. Also it's called jsl, not jslint.
jsl
jslint
Lastly --disable-pylint doesn't work fully. Despite --disable-pylint, configure still creates a pylint target when pylint is available.
--disable-pylint
$ ./configure --disable-pylint --without-jslint $ make pylint ... echo "Pylint is running, please wait ..."; \ PYTHONPATH=. /usr/bin/python -m pylint \ --rcfile=./pylintrc ${FILES} Pylint is running, please wait ... /usr/bin/python: No module named pylint Makefile:1126: recipe for target 'pylint' failed
What is the use case? I what situation would ordinary user run this?
I'm trying to make it easier and more pleasant to build FreeIPA from source. Both pylint and jsl are irrelevant for releases. My direct use case are Python packages from source distributions or git checkouts.
Lukas ran into similar issues and created PR https://github.com/freeipa/freeipa/pull/389.
master:
Metadata Update from @cheimes: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5
TODO: update wiki before closing this ticket
Metadata Update from @cheimes: - Issue close_status updated to: None
Metadata Update from @mbasti: - Issue set to the milestone: FreeIPA 4.5.1 (was: FreeIPA 4.5)
ipa-4-5:
Metadata Update from @pvoborni: - Issue set to the milestone: FreeIPA 4.7 (was: FreeIPA 4.5.1)
FreeIPA's configure script does not require jsl and pylint. Tests are passing.
Metadata Update from @cheimes: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.