So far pam is not really functional as there no pam config files exists, here
we borrow from openembedded to setup core /etc/pam.d to make it functional:
* change 'pam' to 'libpam' following Debian naming convention, and change
(R)DEPENDS in other recipes
* borrow openembedded libpam-base-files with changes:
- rename to libpam-runtime to follow Debian naming
- only keep common-* core files which can be traced back to Debian
libpam-runtime-1.0.1 for license track. Other service specific files
(such as atd, cron, ...) are removed because either they may contaminate
the license or it's right thing to have their own packages providing them
- use same libpam recipe instead of creating a new. This way other /etc/
stuff are all contained by libpam-runtime
* like openembedded, we package each pam plugin into seperate package now,
with some differnce though:
- Some ${sbindir} binaries are bound to specific PAM plugin. So better to
package them together with corresponding plugin package
- populate_sysroot_prepend is invoked before actual populate_sysroot, at
that time ${D} binaries haven't been tripped. So it's difficult to specify
-dev for those plugin pacakges from _prepend which are simply empty.
actually one -dev/-doc per recipe is one good exercise here.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Move the functionality into autotools and ensure all our Poky recipes are no
longer using it.
Keep the autools_stage class around for OE compatability but just have it
inherit autools.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Kevin Tian
Joshua Lock
Richard Purdie
Anas Nashif