Skip to contentSkip to conversation

Remove some recipes that are in OE-Core (cover letter only)

PATCH In review Paul Eggleton 2 participants 4 messages Apr 16, 2013

lore
Share & tools
lore
#0 lore raw

cover Remove some recipes that are in OE-Core (cover letter only)

In case you're wondering why I've only sent the cover letter for just two patches, I tried sending them as normal and what I got was:

fatal: pull-29844/0001-hicolor-icon-theme-remove.patch: 29: patch contains a line longer than 998 characters
warning: no patches were sent

They are just deletes though so they don't contain much in the way of substance.

The following changes since commit a45830a39bb47a9eab27980d52966226c9504ea4:

recipes: Unify indentation (2013-04-15 16:23:17 +0200)

are available in the git repository at:

git://git.openembedded.org/meta-openembedded-contrib paule/meta-gnome
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/meta-gnome

Paul Eggleton (2):
hicolor-icon-theme: remove
libical: remove

 .../hicolor-icon-theme/files/index.theme           | 1731 --------------------
 .../hicolor-icon-theme/hicolor-icon-theme_0.12.bb  |   23 -
 .../libical/files/pthread-fix.patch                |   52 -
 meta-gnome/recipes-support/libical/libical_0.48.bb |   17 -
 4 files changed, 1823 deletions(-)
 delete mode 100644 meta-gnome/recipes-gnome/hicolor-icon-theme/files/index.theme
 delete mode 100644 meta-gnome/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
 delete mode 100644 meta-gnome/recipes-support/libical/files/pthread-fix.patch
 delete mode 100644 meta-gnome/recipes-support/libical/libical_0.48.bb
Signature · 1 line
1.7.10.4
#1 lore raw
Quoted 8 lines · Paul Eggleton

In case you're wondering why I've only sent the cover letter for just two patches, I tried sending them as normal and what I got was:

fatal: pull-29844/0001-hicolor-icon-theme-remove.patch: 29: patch contains a line longer than 998 characters
warning: no patches were sent

They are just deletes though so they don't contain much in the way of substance.

libical is fine and I'll merge it shortly, but hicolor-icon-theme needs PR bump in oe-core first (and in oe-core/dylan if you want it merged in meta-oe before branching dylan).

--- meta-gnome/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb

2013-04-15 16:56:22.777983546 +0200
+++ ../openembedded-core/meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
2013-04-11 17:22:28.077085198 +0200

@@ -8,7 +8,9 @@
SECTION = "unknown"
inherit gnome allarch

-PR = "r1"
+DEPENDS = ""
+
+PR = "r0"

Quoted 33 lines

The following changes since commit a45830a39bb47a9eab27980d52966226c9504ea4:

recipes: Unify indentation (2013-04-15 16:23:17 +0200)

are available in the git repository at:

git://git.openembedded.org/meta-openembedded-contrib paule/meta-gnome
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/meta-gnome

Paul Eggleton (2):
hicolor-icon-theme: remove
libical: remove

 .../hicolor-icon-theme/files/index.theme           | 1731 --------------------
 .../hicolor-icon-theme/hicolor-icon-theme_0.12.bb  |   23 -
 .../libical/files/pthread-fix.patch                |   52 -
 meta-gnome/recipes-support/libical/libical_0.48.bb |   17 -
 4 files changed, 1823 deletions(-)
 delete mode 100644 meta-gnome/recipes-gnome/hicolor-icon-theme/files/index.theme
 delete mode 100644 meta-gnome/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
 delete mode 100644 meta-gnome/recipes-support/libical/files/pthread-fix.patch
 delete mode 100644 meta-gnome/recipes-support/libical/libical_0.48.bb
Signature · 7 lines
1.7.10.4


_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#2 lore raw
Quoted 7 lines · On Tuesday 16 April 2013 16:05:01 Martin Jansa wrote:
Quoted 6 lines · Paul Eggleton

In case you're wondering why I've only sent the cover letter for just two patches, I tried sending them as normal and what I got was:

fatal: pull-29844/0001-hicolor-icon-theme-remove.patch: 29: patch contains a line longer than 998 characters warning: no patches were sent

Quoted 6 lines
Quoted 2 lines

They are just deletes though so they don't contain much in the way of substance.

libical is fine and I'll merge it shortly, but hicolor-icon-theme needs PR bump in oe-core first (and in oe-core/dylan if you want it merged in meta-oe before branching dylan).

If you'll accept an OE-Core PR bump for this can we do the same for the bbappends that are preserved solely for keeping the same PR?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#3 lore raw
Quoted 11 lines · Paul Eggleton
Quoted 10 lines · On Tuesday 16 April 2013 16:05:01 Martin Jansa wrote:
Quoted 8 lines · Paul Eggleton

In case you're wondering why I've only sent the cover letter for just two patches, I tried sending them as normal and what I got was:

fatal: pull-29844/0001-hicolor-icon-theme-remove.patch: 29: patch contains a line longer than 998 characters warning: no patches were sent

They are just deletes though so they don't contain much in the way of substance.

Quoted 6 lines
Quoted 3 lines

libical is fine and I'll merge it shortly, but hicolor-icon-theme needs PR bump in oe-core first (and in oe-core/dylan if you want it merged in meta-oe before branching dylan).

If you'll accept an OE-Core PR bump for this can we do the same for the bbappends that are preserved solely for keeping the same PR?

bbappens are a bit different, because this PR bump (would be nice to do +2) does not need to happen atomically with meta-oe bb removal.

With bbappends it's possible that someone will upgrade oe-core with PR bumps, build qt4-x11-free and then upgrade meta-oe without PRINCs and build qt4-x11-free. But I'm willing to take that risk if we apply both "close" :).

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]