Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom.rini@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Consistency and use cases for IMAGE_FSTYPES
Date: Thu, 22 Mar 2012 14:40:28 -0700	[thread overview]
Message-ID: <20120322214028.GD28378@bill-the-cat> (raw)
In-Reply-To: <20120312202524.GB9300@denix.org>

On Mon, Mar 12, 2012 at 04:25:24PM -0400, Denys Dmytriyenko wrote:
> On Sat, Mar 10, 2012 at 07:29:20AM +0100, Koen Kooi wrote:
> > 
> > Op 9 mrt. 2012, om 22:39 heeft Tom Rini het volgende geschreven:
> > 
> > > Hey all,
> > > 
> > > Over in meta-ti I kicked off a discussion
> > > (https://lists.yoctoproject.org/pipermail/meta-ti/2012-March/000779.html)
> > > about if we should be using '?=' or '+=' with IMAGE_FSTYPES in the
> > > machine conf files.  This has been discussed a little bit before
> > > (http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/2060/focus=2061).
> > > The problem is we have the following and I believe ultimately
> > > conflicting use cases:
> > > - The machine needs to say 'I need or support the following formats'
> > > - The distro needs to say 'I always want format X'
> > > - The user needs to say 'I know best, give me only format X'
> > > - The user needs to say 'I know best, give me what you support + X'
> > > 
> > > We achieve this today, but not very nicely.  For the last one you need
> > > to start playing order of operations games and that's just not nice.
> > > My suggestion is that we need to change what the machine.conf sets to
> > > another variable (SOMETHING_IMAGE_FSTYPES), and a default
> > > IMAGE_FSTYPES becomes ?= ${SOMETHING_IMAGE_FSTYPES}.  Distros, and
> > > users can then work more easily with their use cases.  Comments?
> > 
> > EXTRA_IMAGE_FSTYPES!
> 
> +1
> 
> MACHINE_IMAGE_FSTYPES + DISTRO_IMAGE_FSTYPES? jk :)

Having gotten no other feedback (*cough*) I'll post a patch for
SOMETHING_IMAGE_FSTYPES (I'm leaning MACHINE_IMAGE_FSTYPES, sorry Koen :))
sometime tomorrow I think.

-- 
Tom



  reply	other threads:[~2012-03-22 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 21:39 Consistency and use cases for IMAGE_FSTYPES Tom Rini
2012-03-10  6:29 ` Koen Kooi
2012-03-12 20:25   ` Denys Dmytriyenko
2012-03-22 21:40     ` Tom Rini [this message]
2012-03-22 23:26 ` Richard Purdie
2012-03-22 23:53   ` Denys Dmytriyenko
2012-03-23  1:14     ` Richard Purdie
2012-03-23 15:48       ` Tom Rini
2012-03-23 16:17         ` Darren Hart
2012-03-23 16:29           ` Tom Rini
2012-03-23 16:34             ` Darren Hart
2012-03-23 17:03               ` Tom Rini

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=20120322214028.GD28378@bill-the-cat \
    --to=tom.rini@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