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>
For one, populate-volatile.sh is itself a rcS script which is invoked earlier
than package's own postinst method (last one in rcS). If package has already
installed their volatile files correctly, it doesn't make sense to update volatile
again in postinst since nothing is changed.
On the other hand, dbus/hal are special since their user/group are only created
in the target. If they pre-install volatiles like others, populate-volatile.sh
will report "undefined user" since at that time their user/group haven't been
created. The better way solving this is to generate their volatile in the fly
after user/group are created, and then update volatiles.
This fix [BUGID #121]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
pam recipe is required to build a sato image, and it was moved in the
meta-moblin collection by mistake, and sato build was broken.
pam is a dependency of policykit which is a dependency of networkmanager.
Signed-off-by: Nicolas Dechesne <n-dechesne@ti.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Kevin Tian
Joshua Lock
Nicolas Dechesne
Richard Purdie
Anas Nashif
Anas Nashif