All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] shadow: add a -native recipe with customized utilities
Date: Thu, 1 Sep 2011 19:02:26 -0500	[thread overview]
Message-ID: <4E601D12.6040004@windriver.com> (raw)
In-Reply-To: <1314914360.5939.574.camel@rex>

On 9/1/11 4:59 PM, Richard Purdie wrote:
> On Thu, 2011-09-01 at 20:44 +0100, Phil Blundell wrote:
>> On Thu, 2011-09-01 at 12:25 -0500, Mark Hatle wrote:
>>> On 9/1/11 11:58 AM, Phil Blundell wrote:
>>>> And, I guess, if you want to support online package management then it
>>>> does make some sense to have the shadow utils there.  But I don't
>>>> need/want that in my configuration.
>>>
>>> Does busybox or something else provide a compatible adduser?  If so maybe a
>>> virtual RDEPENDS is more reasonable in this case.
>>
>> I'm not sure offhand (it's actually useradd, not adduser, for what
>> that's worth) but, even if busybox does provide those applets, that
>> probably isn't quite the point.  The issue here is that I don't really
>> want to have any implementation of useradd at all on the target system;
>> using one from busybox would be a bit less bad than requiring standalone
>> shadow, but still not really ideal.
>>
>> One workaround would be to weaken the RDEPENDS to an RRECOMMENDS, which
>> would allow me to declare it as a BAD_RECOMMENDATION.  Or I guess we
>> could make it be a virtual and I could then provide a dummy-useradd
>> package which satisfies the dependency but doesn't actually install any
>> files.  
>>
>> The approach we take with update-rc.d is to let it be installed and then
>> have rootfs_ipk rip it back out again after image construction is done,
>> but this won't work with shadow as it stands due to the postinst issue
>> in that package.  So a third option would be to find a way to finesse
>> the postinst thing somehow and then use the same rootfs_ipk logic with
>> shadow too.
> 
> The latter sounds like what we'll need to do. I haven't looked at shadow
> to see what kind of finessing is required though...
> 
> Does opkg have any notion of bitbake's ASSUME_PROVIDED?

RPM has a mechanism to provide a list of "provided" items.  But there is not
currently any logic to seed that data.  If there is a standard list, it's
something we can add easily enough.

--Mark

> Cheers,
> 
> Richard
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-09-02  0:07 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 18:13 [PATCH 0/7] User/group creation at preinstall Scott Garman
2011-05-31 19:53 ` Scott Garman
2011-05-31 18:13 ` [PATCH 1/7] shadow: recipe and patch cleanup Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-06-01  9:47   ` Phil Blundell
2011-06-01 12:34     ` Martyn Welch
2011-06-01 13:42       ` Phil Blundell
2011-06-01 17:43     ` Scott Garman
2011-06-01 21:05       ` Mark Hatle
2011-06-02 11:19         ` Phil Blundell
2011-09-01 14:46   ` Phil Blundell
2011-09-01 16:41   ` Phil Blundell
2011-09-01 16:54     ` Mark Hatle
2011-09-01 16:58       ` Phil Blundell
2011-09-01 17:25         ` Mark Hatle
2011-09-01 19:44           ` Phil Blundell
2011-09-01 21:59             ` Richard Purdie
2011-09-02  0:02               ` Mark Hatle [this message]
2011-09-02  7:15               ` Phil Blundell
2011-09-02  9:50               ` Phil Blundell
2011-09-02 14:03                 ` Richard Purdie
2011-09-02 18:43                   ` Phil Blundell
2011-09-02 19:17                     ` Mark Hatle
2011-05-31 18:13 ` [PATCH 3/7] base-passwd: add -cross recipe with default login.defs Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 4/7] useradd.bbclass: new class for managing user/group permissions Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 5/7] useradd-example: example recipe for using inherit useradd Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 19:09   ` Mark Hatle
2011-05-31 18:13 ` [PATCH 6/7] bitbake.conf: set PSEUDO_PASSWD within FAKEROOTENV Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:13 ` [PATCH 7/7] package_rpm.bbclass: make RPM use on-disk permissions Scott Garman
2011-05-31 19:53   ` Scott Garman
2011-05-31 18:45 ` [poky] [PATCH 0/7] User/group creation at preinstall Koen Kooi
2011-05-31 18:45   ` Koen Kooi
2011-05-31 19:06   ` [poky] " Saul Wold
2011-05-31 19:06     ` Saul Wold
2011-05-31 19:09     ` Mark Hatle
2011-05-31 19:51     ` [poky] " Scott Garman
2011-05-31 19:51       ` Scott Garman
2011-05-31 19:57       ` [poky] " Otavio Salvador
2011-05-31 21:16         ` Mark Hatle
2011-05-31 21:16           ` [OE-core] " Mark Hatle
2011-05-31 21:27           ` [poky] " Scott Garman
2011-05-31 21:51             ` Richard Purdie
2011-05-31 21:25       ` Richard Purdie
2011-05-31 21:25         ` [OE-core] " Richard Purdie
2011-06-02 23:50 [PATCH 0/7] User/group creation at preinstall v2 Scott Garman
2011-06-02 23:50 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities Scott Garman

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=4E601D12.6040004@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.