From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick Ohly <patrick.ohly@intel.com>, Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] rootfs-postcommands.bbclass: sort passwd entries
Date: Sat, 07 Jan 2017 22:52:08 +0000 [thread overview]
Message-ID: <1483829528.4367.142.camel@linuxfoundation.org> (raw)
In-Reply-To: <1483815653.4383.28.camel@intel.com>
On Sat, 2017-01-07 at 20:00 +0100, Patrick Ohly wrote:
> On Sat, 2017-01-07 at 09:59 +0000, Phil Blundell wrote:
> >
> > On Sat, 2017-01-07 at 09:06 +0100, Patrick Ohly wrote:
> > >
> > >
> > Yes, but there's already a solution for that problem:
> > >
> > > useradd-staticids.bbclass
> > >
> > > I was assuming that someone who wants identical files is already
> > > using
> > > that. Should it be mentioned in a comment next to the new
> > > feature?
> > That sounds like a good idea. And in that case, maybe it would be
> > better to sort on uid rather than username? That would preserve
> > the
> > "traditional" ordering in the file, i.e. root first.
> I had thought about that, but then did not pursue that further
> because
> it would have made sorting quite a bit more complex (needs to know
> about
> line content, id not present in each file).
>
> I can give it a try, though, if that's considered worth some
> additional
> complexity.
I think those functions can be python functions and this might not be
too bad to write in python....
Cheers,
Richard
next prev parent reply other threads:[~2017-01-07 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:38 [PATCH 1/1] rootfs-postcommands.bbclass: sort passwd entries Patrick Ohly
2017-01-06 21:17 ` Phil Blundell
2017-01-07 8:06 ` Patrick Ohly
2017-01-07 9:59 ` Phil Blundell
2017-01-07 19:00 ` Patrick Ohly
2017-01-07 22:52 ` Richard Purdie [this message]
2017-01-08 9:36 ` Phil Blundell
2017-01-08 14:04 ` Patrick Ohly
2017-01-09 10:09 ` [PATCH V2 " Patrick Ohly
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=1483829528.4367.142.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
--cc=pb@pbcl.net \
/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.