lsb

RFC: should libpam be in "utility libraries" instead of "base libraries"?

Bug #1327669 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lsb
In Progress
Low
Unassigned
Mandriva
In Progress
Low

Bug Description

The split of libraries into "Base" and Utility" in LSB Core suggests that pam
ought to be in Utility, or possibly even in the Security submodule. I'm not
sure there is any hard and fast rule, so this is just a request for comments.
But... all of the Base libraries are part of the glibc set, and PAM is not.

http://refspecs.linuxbase.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/baselib.html

http://refspecs.linuxbase.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/utillib.html

The Security submodule is now mandatory and part of the Core module so this is
another possible home, though currently we describe it only as network
security.

Probably the best answer is "change nothing" but we've done a lot of other
rationalization in 5.0 so thought I'd just ask this question.

Tags: future
Changed in mandriva:
importance: Unknown → Low
status: Unknown → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.