Skip to contentSkip to conversation

Design Document of "Yocto 1656 Recipe creation/import script"

DISCUSSION Kang Kai 4 participants 9 messages Jan 6, 2012 – Jan 9, 2012

lore
Share & tools
lore

Kang Kai

author
#0 lore raw

Hi All,

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it. Any suggestion is appreciate.

Regards,
Kai

Design documnet for Recipe creation/import script

* Purpose

The feature is from Yocto 1.2 Bug 1656. A script or similar system that would allow you to give is an upstream URL, tarball, patch set, package (SRPM, or debian style) and generate a recipe based on those instructions.

Name it with bitbake-createbb, and integrate into the build system to use the build system infrastructure that similiar with bitbake-runtask.

* Usage:
bitbake-createbb <SRC_URI> [PATCH_SRC_URI]

* Steps
1 download the source package frowm the SRC_RUI
2 get package name and version from package or tarball name.
3 get summary and description from SRPM spec file or debian control file, or from configure files. 4 get license and license checksum.
5 get dependent packages
|-- just parse spec file or debian control file
|-- or get them by parse configure files
6 remove downloaded files

#1 lore raw
Quoted 8 lines · Kang Kai

Hi All,

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

Regards,
Kai

* s/documnet/document
* s/SRC_RUI/SRC_URI
* reading first time, I thought 'Steps' mean things user has to perform

A bit off-topic: Where is the location for these kind of documents?

Andreas

#3 lore raw
In reply to Kang Kai

Is there any work started regarding this?
Will this be part of bitbake?
Python will be it's "implementation" language?

Best Regards,
Pedro Algarvio.

Quoted 14 lines · Kang Kai

Hi All,

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

Regards,
Kai

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#6 lore raw
In reply to Kang Kai

Hi Kai,

Quoted 3 lines · Kang Kai

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

You should check out autospectacle[1] that I linked to in the bug report. It does a lot of guessing using clever tricks like searching Freshmeat, doap files, READMES etc to get a description[2] and analysing configure.ac[3], qmake[4], etc. to determine dependencies.

The autospectacle perl script is reasonably well commented and quite readable.

I'm not suggesting we adopt all of the features in it but many of them are useful techniques for this effort.

Regards,
Joshua

1. https://meego.gitorious.org/meego-developer-tools/autospectacle/
2. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line1001
3. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line633
4. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line840

Signature · 3 lines
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre
author
#2 lore raw
In reply to Andreas Müller
Quoted 9 lines · Andreas Müller
Quoted 8 lines · Kang Kai

Hi All,

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

Regards,
Kai

Hi Andreas,

Quoted 3 lines

* s/documnet/document
* s/SRC_RUI/SRC_URI
* reading first time, I thought 'Steps' mean things user has to perform

Thanks. I will update them.

Quoted 2 lines

A bit off-topic: Where is the location for these kind of documents?

Do you mean design document? We(WindRiver guys) write it then send it to the mailist.

Regards,
Kai

Quoted 6 lines

Andreas
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

author
#4 lore raw
In reply to Pedro Algarvio

On 2012年01月06日 22:35, Pedro Algarvio wrote:

Hi Pedro,

Quoted 1 line

Is there any work started regarding this?

There is perl script from meego do the similar thing.

Quoted 1 line

Will this be part of bitbake?

I want to put it under directory "scripts"

Quoted 1 line

Python will be it's "implementation" language?

Yes.

Regards,
Kai

Quoted 24 lines

Best Regards,
Pedro Algarvio.

Quoted 6 lines · Kang Kai

Hi All,

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

Quoted 8 lines

Regards,
Kai

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

author
#7 lore raw
In reply to Joshua Lock

On 2012年01月07日 03:18, Joshua Lock wrote:

Hi Joshua,

Quoted 8 lines

Hi Kai,

Quoted 3 lines · Kang Kai

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

You should check out autospectacle[1] that I linked to in the bug report. It does a lot of guessing using clever tricks like searching Freshmeat, doap files, READMES etc to get a description[2] and analysing configure.ac[3], qmake[4], etc. to determine dependencies.

Thanks for your reply.
I have checked out and read the autospectacle, and show me the direction.
Right now I want to get the NAME, description, license and checksum, depends and some simple inheritance, do you think that is enough for this feature? If not, what's more?

Thanks & Regards,
Kai

Quoted 12 lines

The autospectacle perl script is reasonably well commented and quite readable.

I'm not suggesting we adopt all of the features in it but many of them are useful techniques for this effort.

Regards,
Joshua

1. https://meego.gitorious.org/meego-developer-tools/autospectacle/
2. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line1001
3. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line633
4. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line840

author
#5 lore raw
In reply to Kang Kai
Quoted 9 lines · Kang Kai

On 2012年01月06日 22:35, Pedro Algarvio wrote:

Hi Pedro,

Quoted 1 line

Is there any work started regarding this?

There is perl script from meego do the similar thing.

Quoted 1 line

Will this be part of bitbake?

I want to put it under directory "scripts"

My mistake, put it under "bitbake/bin"

Quoted 35 lines
Quoted 2 lines

Python will be it's "implementation" language?

Yes.

Regards,
Kai

Quoted 16 lines

Best Regards,
Pedro Algarvio.

Quoted 10 lines · Kang Kai

Hi All,

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

Regards,
Kai

Quoted 8 lines
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#8 lore raw
In reply to Kang Kai
Quoted 16 lines · Kang Kai

On 2012年01月07日 03:18, Joshua Lock wrote:

Hi Joshua,

Quoted 11 lines

Hi Kai,

Quoted 3 lines · Kang Kai

This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it.
Any suggestion is appreciate.

You should check out autospectacle[1] that I linked to in the bug report. It does a lot of guessing using clever tricks like searching Freshmeat, doap files, READMES etc to get a description[2] and analysing configure.ac[3], qmake[4], etc. to determine dependencies.

Quoted 5 lines

Thanks for your reply.
I have checked out and read the autospectacle, and show me the direction. Right now I want to get the NAME, description, license and checksum, depends and some simple inheritance, do you think that is enough for this feature? If not, what's more?

I think that would be a very good start, yes.

Thanks,
Joshua

Signature · 3 lines
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre