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
--with-initddir in configure should accept "no" #1769
Comments
Comment from firstyear (@Firstyear) at 2016-04-06 10:01:27 attachment |
Comment from nhosoi (@nhosoi) at 2016-04-19 21:44:41 A question about this line. The length of $with_initdir is 0 AND $with_initdir is not "no"? You may want to check the length with '-n'? |
Comment from firstyear (@Firstyear) at 2016-04-20 04:38:43 I think you are right. I want to check if it's not no AND has some content. I'll fix this up. |
Comment from firstyear (@Firstyear) at 2016-04-20 06:24:20 attachment |
Comment from firstyear (@Firstyear) at 2016-04-20 06:24:41 This update, I checked and double check, the logic is correct. |
Comment from nhosoi (@nhosoi) at 2016-04-20 21:46:36 Looks good. Thanks. |
Comment from firstyear (@Firstyear) at 2016-04-26 06:51:19 commit 5c72fee72abfcb5b2d064eb9a640732317d539b1 |
Comment from firstyear (@Firstyear) at 2017-02-11 23:07:22 Metadata Update from @Firstyear:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48447
Our configure script has the current logic:
If systemd:
- disable
else:
- always use initddir
This isn't good form for porting to other distros. initddir should accept ="no" to prevent the creation of /etc/init.d/rc.d scripts.
The text was updated successfully, but these errors were encountered: