[yocto] wic status

[Rifenbark, Scott M]

So tomorrow I should have an updated version of that wic section in the dora branch of the docs.  I will need Tom to look at it.  I am making some changes based on the write up I got from that first email thread Tom sent out.  Then, based on that copy in the 1.5.x docs, I will get the section into the daisy branch and the master branch.  Tom - I will send you a note and link when it is ready for review. 

Scott

>-----Original Message-----
>From: yocto-bounces at yoctoproject.org [mailto:yocto-
>bounces at yoctoproject.org] On Behalf Of Maciek Borzecki
>Sent: Thursday, July 17, 2014 10:39 AM
>To: Tom Zanussi
>Cc: Paul Eggleton; Scott Rifenbark; yocto at yoctoproject.org
>Subject: Re: [yocto] wic status
>
>On czw, 2014-07-17 at 09:18 -0500, Tom Zanussi wrote:
>> On Thu, 2014-07-17 at 14:51 +0100, Paul Eggleton wrote:
>> > On Thursday 17 July 2014 16:48:41 Scott Rifenbark wrote:
>> > > On Thu, Jul 17, 2014 at 3:56 PM, Paul Eggleton <
>> > > paul.eggleton at linux.intel.com> wrote:
>> > > > On Thursday 17 July 2014 14:25:16 Maciek Borzecki wrote:
>> > > > > 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.h
>> > > > > tml
>> > > > >
>> > > > > 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-
>manua
>> > > > > l.html
>> > > >
>> > > > Scott, can you take a look at this if you haven't already?
>> > >
>> > > wic was documented in the 1.5.x set and was not put into the 1.6
>> > > set.  I was told that it was going to change or be further
>> > > completed so it did not go in that development branch.  Wic was never
>documented in the 1.6 set.
>> >
>> > Well, wic is still a part of the system in 1.6 and beyond so we do
>> > need to document it; as far as I can tell what was in the 1.5 manual
>> > linked above should be perfectly fine and we can just extend /
>> > update it as needed. Tom should be able to help fill in any blanks.
>> >
>>
>> Right, wic is still included in the system, and like the rest of the
>> system is undergoing continual development, so I'm not sure why it
>> would be treated differently.
>>
>> In any case, to make it easier for users and to avoid a mismatch with
>> external documentation, over the past couple weeks I've submitted a
>> set of patches (which have now been merged) that puts most of the help
>> content into the tool itself, which is all now accessible via 'wic
>> help'.
>
>Right, I've seen your patches in master, very helpful.
>
>There's one more thing that I'm a bit confused about. The 1.5.2 docs state the
>following:
>
><excerpt start>
>Here are the actual partition language commands used in the mkefidisk.wks
>file to generate an image:
>
>     # short-description: Create an EFI disk image
>     # long-description: Creates a partitioned EFI disk image that the user
>     # can directly dd to boot media.
>
>     part /boot --source bootimg --ondisk sda --fstype=efi --label msdos --active
>--align 1024 <excerpt end>
>
>I'd assume to find scripts/lib/mic/plugins/source/bootimg.py in the tree, but
>the file is not there. Have I missed something?
>
>(btw. I'm also assuming that bootimg would prepare a boot partitiong without
>pushing any particular bootloader, like syslinux or whatever
>right?)
>
>
>--
>Maciej Borzęcki
>Senior Software Developer at Open-RnD Sp. z o.o., Poland www.open-rnd.pl
>mobile: +48 889 117 365, fax: +48 42 657 9079
>
>Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem
>lub poufne informacje i została wysłana wyłącznie do wiadomości i użytku
>osób, do których została zaadresowana. Jeśli wiadomość została otrzymana
>przypadkowo zabrania się jej kopiowania lub rozsyłania do osób trzecich. W
>takim przypadku uprasza się o natychmiastowe zniszczenie wiadomości oraz
>poinformowanie nadawcy o zaistniałej sytuacji za pomocą wiadomości
>zwrotnej. Dziękujemy.
>
>This message, including any attachments hereto, may contain privileged or
>confidential information and is sent solely for the attention and use of the
>intended addressee(s). If you are not an intended addressee, you may
>neither use this message nor copy or deliver it to anyone. In such case, you
>should immediately destroy this message and kindly notify the sender by
>reply email. Thank you.
>
>
>--
>_______________________________________________
>yocto mailing list
>yocto at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto