Bug 2218323 - Separate out 'ldap' functionality into its own package
Summary: Separate out 'ldap' functionality into its own package
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: sudo
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Radovan Sroka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-28 18:24 UTC by quanah.gibsonmount
Modified: 2024-05-28 13:16 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:16:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description quanah.gibsonmount 2023-06-28 18:24:57 UTC
The current sudo package does not separate out ldap functionality into its own package, forcing the installation of the "openldap" package onto systems unnecessarily.  It would be better to follow the superior debian strategy of making a separate package "sudo-ldap" for those who need to integrate with LDAP.

Reproducible: Always

Steps to Reproduce:
1. Install sudo
2. See openldap package forced in as a requirement.
3.


Expected Results:  
It should be possible to install sudo without having the 'openldap' package installed.

There's no reason for everyone to have to install the openldap package purely because sudo was installed.

Comment 1 Aoife Moloney 2024-05-28 13:16:11 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.