From: Bob Cochran <yocto@mindchasers.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
Yocto discussion list <yocto@yoctoproject.org>
Cc: paul@paulbarker.me.uk,
bitbake-dev <bitbake-devel@lists.openembedded.org>
Subject: Re: [yocto] newbb.vim vs skeleton recipe in yocto-docs dev manual....
Date: Tue, 18 Nov 2014 22:01:55 -0500 [thread overview]
Message-ID: <546C0823.6060808@mindchasers.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237988E52758@ORSMSX101.amr.corp.intel.com>
On 11/10/2014 09:28 AM, Rifenbark, Scott M wrote:
> newbb.vim needs to be patched.
I have a patch ready to bring newbb.vim in line with Section 5.3.2 of
the Yocto Project Dev Manual. However, I'm wondering whether I can
drop the initial two lines of the generated file (I think I should):
# Copyright (C) 2014 <user_name> <user_email>
# Released under the MIT license (see COPYING.MIT for the terms)
This seems inconsistent with the recipes I see in the Yocto / OE layers
and the Yocto documentation.
The patch I created, which is provided below for reference, comments out
the generation of these first two lines:
--- a/bitbake/contrib/vim/plugin/newbb.vim
+++ b/bitbake/contrib/vim/plugin/newbb.vim
@@ -44,21 +44,31 @@ fun! NewBBTemplate()
let l:paste = &paste
set nopaste
- " Get the header
- call BBHeader()
+ " Uncomment the line below to enable header generation
+ "call BBHeader()
" New the bb template
+ 0 put ='SUMMARY = \"\"'
put ='DESCRIPTION = \"\"'
put ='HOMEPAGE = \"\"'
put ='LICENSE = \"\"'
- put ='SECTION = \"\"'
+ put ='LIC_FILES_CHKSUM = \"\"'
+ put =''
put ='DEPENDS = \"\"'
put =''
put ='SRC_URI = \"\"'
+ put ='SRC_URI[md5sum] = \"\"'
+ put ='SRC_URI[sha256sum] = \"\"'
+ put =''
+ put ='S = \"${WORKDIR}/${PN}-${PV}\"'
+ put =''
+ put ='#inherit <classes>'
+
+
" Go to the first place to edit
0
- /^DESCRIPTION =/
+ /^SUMMARY =/
exec "normal 2f\""
if paste == 1
thanks
Bob
>
> Scott
>
>> -----Original Message-----
>> From: yocto-bounces@yoctoproject.org [mailto:yocto-
>> bounces@yoctoproject.org] On Behalf Of Bob Cochran
>> Sent: Sunday, November 09, 2014 1:14 PM
>> To: Yocto discussion list
>> Subject: [yocto] newbb.vim vs skeleton recipe in yocto-docs dev manual....
>>
>> Hi,
>>
>> I just noticed that newbb.vim in bitbake/contrib is notably different from the
>> skeleton recipe proposed in the latest Dev Manual.
>>
>> I'll submit a patch if someone can give me some guidance on what should be
>> in newbb.vim (or maybe it's the manual that needs to be patched).
>>
>> Bob
>>
>>
>> From yocto-docs: Dev Manual (modify the following skeleton recipe):
>>
>> SUMMARY = ""
>> HOMEPAGE = ""
>> LICENSE = ""
>> LIC_FILES_CHKSUM = ""
>> SRC_URI = ""
>> SRC_URI[md5sum] = ""
>> SRC_URI[sha256sum] = ""
>> S = "${WORKDIR}/${PN}-${PV}"
>>
>>
>>
>> From newbb.vim:
>>
>> DESCRIPTION = ""
>> HOMEPAGE = ""
>> LICENSE = ""
>> SECTION = ""
>> DEPENDS = ""
>>
>> SRC_URI = ""
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
parent reply other threads:[~2014-11-19 3:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <41DEA4B02DBDEF40A0F3B6D0DDB1237988E52758@ORSMSX101.amr.corp.intel.com>]
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=546C0823.6060808@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
--cc=scott.m.rifenbark@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox