#1129 wrong build dependency on nscd
Closed: Fixed None Opened 12 years ago by simo.

We currently have a build dependency on nscd in the contributed spec file.
That's because we use a configure script to find nscd binaries locations.

We should keep the configure check and use it to locate binaries. But we shouldn't have ifdefs in the code. The nscd presence is basically a runtime check, as we do not have a hard depdnency on nscd otherwise.

So when configure checks fails we should simply use a reasonable default settable by a configure switch.

This will allow us to eliminate the BuildRequires on nscd


Fields changed

summary: wrong build depdnency on nscd => wrong build dependency on nscd

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.8.0

Fields changed

feature_milestone: =>
owner: somebody => sgallagh
patch: 0 => 1
status: new => assigned

Fixed by:
- 3b917f1 (master)
- 7b97370 (sssd-1-8)

component: SSSD => Build Environment
resolution: => fixed
status: assigned => closed

Metadata Update from @simo:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.8.0 (LTM)

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2171

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata