From Fedora Project Wiki
< Changes
(Libuser removal from Fedora) |
No edit summary |
||
| Line 7: | Line 7: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= Removing libuser from Fedora = | = Removing libuser and passwd from Fedora = | ||
{{Change_Proposal_Banner}} | {{Change_Proposal_Banner}} | ||
| Line 40: | Line 40: | ||
[[Category:SystemWideChange]] | [[Category:SystemWideChange]] | ||
* Targeted release: [https://docs.fedoraproject.org/en-US/releases/ | * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f39/ Fedora Linux 39] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 55: | Line 55: | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
The libuser provides library and command line utilities to manipulate user and group information. The purpose of the library | |||
is/was to hide the differences between users in LDAP and files in etc (passwd, groups...). The support for LDAP | |||
is not complete and there is no plan to extend the functionality. | |||
The LDAP integration in Fedora is nowadays done by SSSD. | |||
In the past, the libuser was used by more component including Fedora installer. Currently the list is short | |||
* usermode (Requires development, it is not complicated but the dependency is unconditional) | |||
* util-linux (compile time option) | |||
* passwd (I suggest to ship passwd utility from shadow-utils instead of passwd and drop passwd package as well) | |||
== Feedback == | == Feedback == | ||
| Line 87: | Line 100: | ||
https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | ||
--> | --> | ||
The main benefit is to decrease the maintenance and packaging work on library that does not bring much value while the functionality is provided by another components. | |||
== Scope == | == Scope == | ||
| Line 92: | Line 106: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: | * Other developers: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
** Update usermode code to make libuser dependency configurable. | |||
** Update usermode packaging to compile it without libuser | |||
** Change packaging of util-linux to compile without libuser dependency | |||
** Change packaging of shadow-utils to provide passwd utility | |||
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Revision as of 09:37, 20 June 2023
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Guidance
For details on how to fill out this form, see the documentation.
For details on how to fill out this form, see the documentation.
Report issues
To report an issue with this template, file an issue in the pgm_docs repo.
To report an issue with this template, file an issue in the pgm_docs repo.
Removing libuser and passwd from Fedora
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Libuser is not actively developed. Most of the depending component have build-time option to work without libuser.
Owner
- Name: Tomas Halman
- Email: <thalman@redhat.com>
Current status
- Targeted release: Fedora Linux 39
- Last updated: 2023-06-20
- [<will be assigned by the Wrangler> devel thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
The libuser provides library and command line utilities to manipulate user and group information. The purpose of the library is/was to hide the differences between users in LDAP and files in etc (passwd, groups...). The support for LDAP is not complete and there is no plan to extend the functionality.
The LDAP integration in Fedora is nowadays done by SSSD.
In the past, the libuser was used by more component including Fedora installer. Currently the list is short
- usermode (Requires development, it is not complicated but the dependency is unconditional)
- util-linux (compile time option)
- passwd (I suggest to ship passwd utility from shadow-utils instead of passwd and drop passwd package as well)
Feedback
Benefit to Fedora
The main benefit is to decrease the maintenance and packaging work on library that does not bring much value while the functionality is provided by another components.
Scope
- Proposal owners:
- Other developers:
- Update usermode code to make libuser dependency configurable.
- Update usermode packaging to compile it without libuser
- Change packaging of util-linux to compile without libuser dependency
- Change packaging of shadow-utils to provide passwd utility
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Community Initiatives:
Upgrade/compatibility impact
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)