[oe] [PATCH] opkg-utils: Update SRC_URI to git.yoctoproject.org

Apelete Seketeli apelete at seketeli.net
Thu Apr 12 20:44:17 UTC 2012


Le 11-Apr-12, Martin Jansa a écrit:
> On Wed, Apr 11, 2012 at 11:46:32PM +0200, Apelete Seketeli wrote:
> > This updates SRC_URI as the svn.openmoko.org repository is now down.
> > All the changes of this patch were picked from oe-core and brought
> > over.
> > 
> > Signed-off-by: Apelete Seketeli <apelete at seketeli.net>
> > ---
> >  .../opkg-utils/opkg-utils/add-license-field.patch  |   39 +++++++++++++++++
> >  .../opkg-utils/arfile_header_split.patch           |   10 +++++
> >  .../opkg-utils/index-ignore-filenotfound.patch     |   19 ++++++++
> >  recipes/opkg-utils/opkg-utils/mtime-int.patch      |    3 ++
> >  recipes/opkg-utils/opkg-utils/shebang.patch        |   46 ++++++++++++++++++++
> >  recipes/opkg-utils/opkg-utils_git.bb               |   31 +++++++++++++
> >  recipes/opkg-utils/opkg-utils_svn.bb               |   27 ------------
> >  7 files changed, 148 insertions(+), 27 deletions(-)
> >  create mode 100644 recipes/opkg-utils/opkg-utils/add-license-field.patch
> >  create mode 100644 recipes/opkg-utils/opkg-utils/shebang.patch
> >  create mode 100644 recipes/opkg-utils/opkg-utils_git.bb
> >  delete mode 100644 recipes/opkg-utils/opkg-utils_svn.bb
> 
> All those patches were sent as git patches for git.yoctoproject.org.. so 
> you can ping yocto ML to apply them sooner then after 1.2 release to make this patch
> a bit smaller :).
> 
> See
> https://lists.yoctoproject.org/pipermail/yocto/2012-March/007851.html

Sorry for the giant patch, I wasn't sure if I should split it since
the patch files in the commit are needed for the recipe to work.

Concerning the patches sent to the yocto ML, we may have a
misunderstanding here.
This patch I sent is picked from oe-core and I would like someone to
review it and ultimately apply it to *oe-classic* (I need it for the
jlime distribution, which is only available in oe-classic for now).
It seemed to me that the yocto project is based on oe-core, so I don't
understand why I should get in touch with them to get some part of the
changes applied on their side (of oe-core, if I am not mistaken).

I probably missed some point you were trying to make, could you tell
me how to get this into oe-classic ?

Regards.
-- 
        Apelete




More information about the Openembedded-devel mailing list