Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] packagegroup-core-basic: libuser has a hard depenency on libpam
Date: Wed, 16 Oct 2013 13:24:09 +0100	[thread overview]
Message-ID: <1381926249.29912.465.camel@ted> (raw)
In-Reply-To: <4C04C210-DFEA-46BB-B322-9EB80ED0E0B5@dominion.thruhere.net>

On Wed, 2013-10-16 at 14:21 +0200, Koen Kooi wrote:
> Op 16 okt. 2013, om 13:47 heeft Paul Eggleton <paul.eggleton@linux.intel.com> het volgende geschreven:
> 
> > On Wednesday 16 October 2013 13:23:08 Koen Kooi wrote:
> >> Op 16 okt. 2013, om 12:25 heeft Paul Eggleton
> >> <paul.eggleton@linux.intel.com> het volgende geschreven:
> >>> On Tuesday 15 October 2013 15:22:46 Saul Wold wrote:
> >>>> Since libpam is only built when DISTRO_FEATURES pam is enabled we should
> >>>> not be trying to build libuser also.
> >>> 
> >>> Should this packagegroup be bringing in libraries such as this at all,
> >>> given that libraries are generally pulled in as dependencies of
> >>> applications that link to them?
> >> 
> >> If it is a pure library, no. But libuser doesn't seem to be a pure library
> >> package:
> >> 
> >> [koen@rrMBP libuser]$ cat libuser/latest
> >> PV = 0.58
> >> PR = r0
> >> PKGR = r0.0
> >> RPROVIDES =
> >> RDEPENDS = eglibc (>= 2.17) glib-2.0 (>= 2.34.3) libffi (>= 3.0.11) libpam
> >> (>= 1.1.6) popt (>= 1.16) RRECOMMENDS =
> >> PKGSIZE = 283679
> >> FILES = /usr/bin/* /usr/sbin/* /usr/lib/libuser/* /usr/lib/lib*.so.* /etc
> >> /com /var /bin/* /sbin/* /lib/*.so.* /lib/udev/rules.d
> >> /usr/lib/udev/rules.d /usr/share/libuser /usr/lib/libuser/*
> >> /usr/share/pixmaps /usr/share/applications /usr/share/idl /usr/share/omf
> >> /usr/share/sounds /usr/lib/bonobo/servers FILELIST = /etc/libuser.conf
> >> /usr/bin/lchfn /usr/bin/lchsh /usr/lib/libuser.so.1
> >> /usr/lib/libuser.so.1.4.0 /usr/lib/libuser/libuser_files.so
> >> /usr/lib/libuser/libuser_shadow.so /usr/sbin/lchage /usr/sbin/lgroupadd
> >> /usr/sbin/lgroupdel /usr/sbin/lgroupmod /usr/sbin/lid /usr/sbin/lnewusers
> >> /usr/sbin/lpasswd /usr/sbin/luseradd /usr/sbin/luserdel /usr/sbin/lusermod
> > 
> > Right, in that case, ignore me :)
> 
> But I still don't know what it does and why it needs to be in packagegroup-core-basic, though.

Looks like it has a number of pam user tools (groupadd, useradd and so
on) and this goes with the other contents of
packagegroup-core-multiuser...

Cheers,

Richard



      reply	other threads:[~2013-10-16 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 22:22 [PATCH] packagegroup-core-basic: libuser has a hard depenency on libpam Saul Wold
2013-10-16 10:25 ` Paul Eggleton
2013-10-16 11:23   ` Koen Kooi
2013-10-16 11:47     ` Paul Eggleton
2013-10-16 12:21       ` Koen Kooi
2013-10-16 12:24         ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1381926249.29912.465.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox