From: Philip Balister <philip@balister.org>
To: maciej.borzecki@open-rnd.pl, yocto@yoctoproject.org
Subject: Re: wic status
Date: Thu, 17 Jul 2014 08:46:24 -0400 [thread overview]
Message-ID: <53C7C5A0.60201@balister.org> (raw)
In-Reply-To: <1405599916.4781.2.camel@localhost.localdomain>
On 07/17/2014 08:25 AM, Maciek Borzecki wrote:
> Hi,
>
> There used to be an entry about wic in development manual back in 1.5.2:
> http://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html
I'm not sure where the docs are, but people are responding to bug
reports about wic with patches :)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6513
Philip
>
> This entry is gone in current documentation and there seems to be no
> mention of wic at all:
> https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
>
> Does this mean that wic is deprecated? If so what is the current method
> of creating partitioned images?
>
> I'm a bit confused as it seems meta-raspberrypi keeps maitaining
> sdcard_image-rpi.bbclass, Freescale has their image_types_fsl.bbclass.
> In meta-ti, there was this commit:
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=2b524321a25c35c5f987b8331e41b49d3b2e2d2b that effectively removed sdclass_image.bbclass, indicating that wic is the new way.
>
next prev parent reply other threads:[~2014-07-17 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 12:25 wic status Maciek Borzecki
2014-07-17 12:46 ` Philip Balister [this message]
2014-07-17 12:56 ` Paul Eggleton
[not found] ` <CAFNP8Os559bt59bx6tfqp+R+HyUxz66kaxjuvzBGiRKbdUMjdQ@mail.gmail.com>
2014-07-17 13:51 ` Paul Eggleton
2014-07-17 14:06 ` Tom Zanussi
2014-07-17 14:18 ` Tom Zanussi
2014-07-17 17:38 ` Maciek Borzecki
2014-07-17 18:28 ` Rifenbark, Scott M
2014-07-17 20:07 ` Tom Zanussi
2014-07-18 14:12 ` Maciek Borzecki
2014-07-17 13:52 ` Maciek Borzecki
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=53C7C5A0.60201@balister.org \
--to=philip@balister.org \
--cc=maciej.borzecki@open-rnd.pl \
--cc=yocto@yoctoproject.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.