From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] package_ipk: correct ipk descriptions
Date: Mon, 29 May 2017 12:24:53 -0500 [thread overview]
Message-ID: <1496078693.26945.48.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZUsLuPFgEb-G79VVhBxsNKstenHgk_V-njU51YRGotAg@mail.gmail.com>
On Wed, 2017-05-24 at 23:08 +0100, Burton, Ross wrote:
>
> On 24 May 2017 at 21:47, Leonardo Sandoval
> <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
> I will check that particular recipe and bb world just so see
> if some
> other recipe is broken with this change, then provide a v3.
>
>
> And double check what opkg expects :)
>
Right. in my narrow Google search I can see that ipk is poorly
documented but this is what I found from web archive [1]
"Description should be a short, (less than 80 characters) description of
the program. It may also include a long description on subsequent lines,
(each indented by a single space character). Blank lines in the long
description may be indicated by a line consisting of a space character
followed by a period, ie " ."
So a multiline description, every line (including the first one) must
have a leading space. I tried the latter and worked so v3 to be sent
soon.
https://web.archive.org/web/20100727133051/http://handhelds.org:80/moin/moin.cgi/BuildingIpkgs
>
> Ross
next prev parent reply other threads:[~2017-05-29 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 19:26 [PATCH] package_ipk.bbclass: Include a space followed by a dot for empty description lines leonardo.sandoval.gonzalez
2017-05-04 11:13 ` Burton, Ross
2017-05-22 16:43 ` [PATCH v2] package_ipk: correct ipk descriptions leonardo.sandoval.gonzalez
2017-05-24 20:15 ` Burton, Ross
2017-05-24 20:47 ` Leonardo Sandoval
2017-05-24 22:08 ` Burton, Ross
2017-05-29 17:24 ` Leonardo Sandoval [this message]
2017-05-29 17:36 ` [PATCH v3] package_ipk: correct ipk multiline descriptions leonardo.sandoval.gonzalez
2017-05-29 21:41 ` Andreas Oberritter
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=1496078693.26945.48.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.