Bug 10513 - Make PAM security install directory configurable at compile time
Make PAM security install directory configurable at compile time
Status: RESOLVED FIXED
Product: CifsVFS
Classification: Unclassified
Component: user space tools
2.6
All All
: P5 normal
: ---
Assigned To: Jeff Layton
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-21 15:22 UTC by Lars Müller
Modified: 2015-09-01 10:47 UTC (History)
0 users

See Also:


Attachments
Make the PAM security dir configureable (1.72 KB, patch)
2014-03-21 15:22 UTC, Lars Müller
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Müller 2014-03-21 15:22:55 UTC
Created attachment 9796 [details]
Make the PAM security dir configureable

At the moment pamdir is defined fix as $(libdir)/security  With the added patch we're able to configure --with-pamdir=/%{_lib}/security for example.
Comment 1 Jeff Layton 2014-03-21 17:55:28 UTC
Basic concept looks good. Makefile.in is autogenerated so there's no need to patch that. The rest looks fairly straightforward and shouldn't cause any change by default. I'll give it a test when I have some time and verify it.
Comment 2 Jeff Layton 2014-04-02 14:29:27 UTC
Thanks for the patch. I made a few small tweaks, and sent it out to the list. I'll plan to merge it in the next day or two if no one objects.