Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] 'wic'- OpenEmbedded Image Creator
Date: Sun, 29 Sep 2013 20:18:33 -0500	[thread overview]
Message-ID: <1380503913.31937.161.camel@empanada> (raw)
In-Reply-To: <CALmOhgmcxAgG2D3SNYiH_OK_nxMRKUmsWhLi9VAjqxO7kJH7MQ@mail.gmail.com>

On Sat, 2013-09-28 at 13:10 -0400, Trevor Woerner wrote:
> On 26 September 2013 22:17, Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> > This patchset implements a new command named 'wic' (for OpenEmbedded
> > Image Creator).  Please see [YOCTO #3847] for extensive background on
> > what's implemented here.
> 
> Wow Tom, this is really AWESOME work! And thanks for the excellent
> detailed description of the current system which you documented in
> [YOCTO #3847]!
> 

Thanks!

> One question comes to mind: if I have a package which installs files
> to two (or more) different directories and I have decided (for
> whatever reason) that those directories should be on separate
> partitions, is this supported?

No, the current code doesn't, but what I had planned on doing was adding
hyphenated suffixes onto the --source rootfs param which would be
treated as subdividing the rootfs (passed in using -r) and creating
separate partitions with those contents e.g.

--source rootfs-home
--source rootfs-usr-local

So in the above, the contents of /home would be split out into a
separate partition (and subtracted from rootfs) as well as /usr/local,
and fstab entries would be created to mount those partitions as /home
and /usr/local...

Tom 

> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core




      reply	other threads:[~2013-09-30  1:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  2:17 [PATCH 0/3] 'wic'- OpenEmbedded Image Creator Tom Zanussi
2013-09-27  2:17 ` [PATCH 1/3] wic: Initial code for wic (OpenEmbedded Image Creator) Tom Zanussi
2013-09-27 14:01   ` Otavio Salvador
2013-09-27 14:21     ` Tom Zanussi
2013-09-28 12:17       ` David Nyström
2013-09-30  1:11         ` Tom Zanussi
2013-09-30 12:58           ` David Nyström
2013-09-30 15:15             ` Tom Zanussi
2013-09-27  2:17 ` [PATCH 2/3] wic: Add mic w/pykickstart Tom Zanussi
2013-09-27  2:17 ` [PATCH 3/3] wic: Add OpenEmbedded-specific implementation Tom Zanussi
2013-09-27  6:48 ` [PATCH 0/3] 'wic'- OpenEmbedded Image Creator David Nystrom
2013-09-27 13:32   ` Tom Zanussi
2013-09-28 17:10 ` Trevor Woerner
2013-09-30  1:18   ` Tom Zanussi [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=1380503913.31937.161.camel@empanada \
    --to=tom.zanussi@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=trevor.woerner@linaro.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