All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: Please help to review the Yocto 1656: Recipe creation/import script
Date: Thu, 19 Jan 2012 11:57:40 +0000	[thread overview]
Message-ID: <4677690.3hU1sHNFnX@helios> (raw)
In-Reply-To: <4F17E37B.7030506@windriver.com>

Hi Kai,

On Thursday 19 January 2012 17:33:47 Kang Kai wrote:
> The attachment is the the design document V2 and implement.
> 
> The V2 document changes are:
> 1 remove patch_set from argument list
> 2 deb is not support right now
> 
> Any comment is welcome.
> And I will on vacation until Jan 30, so my reply may not in time.

Great work! I can see this being really useful to help people get started with 
new recipes. A few comments:

1) I tried it on hdparm and it worked very well. However, obexftp caused an 
error:

----------------
Downloading package:  
http://downloads.sourceforge.net/openobex/obexftp-0.23.tar.bz2  to  
/tmp/bitbake_createbb.5729
Traceback (most recent call last):
  File "./bitbake-createbb", line 643, in <module>
    process_configure(pkgdir)
  File "./bitbake-createbb", line 295, in process_configure
    if match and len(pkgname) == 0:
UnboundLocalError: local variable 'pkgname' referenced before assignment
----------------

2) If it is able to find license file(s) but unable to find any appropriate for 
LIC_FILES_CHKSUM, it would be nice if it would print a warning just so the 
user knows they will need to set this themselves (bonus points if you still 
list LIC_FILES_CHKSUM entries for license files that did not match the known 
checksums either in a comment in the output or in the warning message, to save 
the user work if they know the files are appropriate). If you prefer I can send 
a patch afterwards for this.

3) If you have an RPM spec file it is possible to extract PACKAGES and FILES 
and possibly even EXTRA_OECONF. Somewhere around here I have a very basic 
script to do this I think, I could send it to you if you like (or we can leave 
this for later).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2012-01-19 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F17C7D9.10506@windriver.com>
2012-01-19  9:33 ` Please help to review the Yocto 1656: Recipe creation/import script Kang Kai
2012-01-19 11:57   ` Paul Eggleton [this message]
2012-01-19 16:33   ` Mark Hatle
2012-01-30  2:21     ` Kang Kai
2012-01-20  1:57   ` Joshua Lock

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=4677690.3hU1sHNFnX@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=Kai.Kang@windriver.com \
    --cc=poky@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.