From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Allow xuser to shutdown
Date: Thu, 04 Jul 2013 10:24:09 +0300 [thread overview]
Message-ID: <51D52319.7030302@intel.com> (raw)
In-Reply-To: <20130703161921.GB3452@jama>
On 07/03/2013 07:19 PM, Martin Jansa wrote:
> On Wed, Jul 03, 2013 at 05:34:20PM +0300, Laurentiu Palcu wrote:
>> The following changes since commit 8a186a6b3853fc1a7dcf342d421c8926c38949c9:
>>
>> bitbake: hob: save button from settings called a nonexisting method (2013-07-03 08:13:35 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib lpalcu/b4345_shutdown_icon_rootless_x
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lpalcu/b4345_shutdown_icon_rootless_x
>>
>> Laurentiu Palcu (4):
>> sysvinit: allow users in shutdown group to perform halt/reboot
>> connman: make xuser a member of 'shutdown' group
>> xserver-nodm-init: make xuser a member of 'shutdown' group
>> shutdown-desktop: give entire path in Exec field
>
> Shouldn't we create separate recipe for xuser or any other default user
> and add it to connman and xserver-nodm-init RDEPENDS?
>
> I know there is some overhead from having one more package installed on
> image, but it would be a bit easier if we later decide that xuser also
> needs some file to be installed in his home or something like that.
I can see one advantage of having a separate recipe for xuser: the user
creation would be done in one place and we souldn't have to change in
two places if we want to add the user to another group (for example).
It sounds a good change to me.
Laurentiu
>
>> meta/recipes-connectivity/connman/connman.inc | 2 +-
>> meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 12 +++++++++---
>> .../x11-common/xserver-nodm-init.bb | 2 +-
>> .../shutdown-desktop/shutdown-desktop.bb | 2 +-
>> .../shutdown-desktop/shutdown.desktop | 4 ++--
>> 5 files changed, 14 insertions(+), 8 deletions(-)
>>
>> --
>> 1.7.9.5
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-07-04 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 14:34 [PATCH 0/4] Allow xuser to shutdown Laurentiu Palcu
2013-07-03 14:34 ` [PATCH 1/4] sysvinit: allow users in shutdown group to perform halt/reboot Laurentiu Palcu
2013-07-03 14:34 ` [PATCH 2/4] connman: make xuser a member of 'shutdown' group Laurentiu Palcu
2013-07-03 14:34 ` [PATCH 3/4] xserver-nodm-init: " Laurentiu Palcu
2013-07-03 14:34 ` [PATCH 4/4] shutdown-desktop: give entire path in Exec field Laurentiu Palcu
2013-07-03 15:40 ` [PATCH 0/4] Allow xuser to shutdown Laurentiu Palcu
2013-07-03 16:19 ` Martin Jansa
2013-07-04 7:24 ` Laurentiu Palcu [this message]
2013-07-04 8:54 ` Tomas Frydrych
2013-07-04 11:03 ` Burton, Ross
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=51D52319.7030302@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox