Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>,
	openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCHv2 2/2] net-snmp: Update to 5.7.2
Date: Wed, 17 Apr 2013 13:10:42 +0200	[thread overview]
Message-ID: <20130417111042.GF26007@jama> (raw)
In-Reply-To: <1366195597-13363-2-git-send-email-ml@communistcode.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2135 bytes --]

On Wed, Apr 17, 2013 at 11:46:37AM +0100, Jack Mitchell wrote:
> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
> 
> - Removed some un-needed patches
> 
> diff --git a/meta-oe/recipes-extended/net-snmp/net-snmp_5.7.1.bb b/meta-oe/recipes-extended/net-snmp/net-snmp_5.7.2.bb
> similarity index 76%
> rename from meta-oe/recipes-extended/net-snmp/net-snmp_5.7.1.bb
> rename to meta-oe/recipes-extended/net-snmp/net-snmp_5.7.2.bb
> index 19aa163..048ecb8 100644
> --- a/meta-oe/recipes-extended/net-snmp/net-snmp_5.7.1.bb
> +++ b/meta-oe/recipes-extended/net-snmp/net-snmp_5.7.2.bb
> @@ -1,11 +1,8 @@
>  require net-snmp.inc
>  
> -PR = "${INC_PR}.4"

This can surprise people editing net-snmp.inc and bumping INC_PR there
without any effect on net-snmp_5.7.2.bb.

I understand why you wanted to remove it, but I would prefer to keep
PR = "${INC_PR}.0" there as long as we have .inc with INC_PR.

I wouldn't mind merging .inc in .bb as people probably don't have own
versions of net-snmp in their layers (just guessing here).

And it was send to wrong ML this time..

>  LIC_FILES_CHKSUM = "file://README;beginline=3;endline=8;md5=7f7f00ba639ac8e8deb5a622ea24634e"
>  
>  SRC_URI = "${SOURCEFORGE_MIRROR}/net-snmp/net-snmp-${PV}.tar.gz \
> -        file://sync-with-5.7-branch.patch \
> -        file://libnl-3-support.patch \
>          file://init \
>          file://snmpd.conf \
>          file://snmptrapd.conf \
> @@ -30,5 +27,5 @@ do_configure_prepend() {
>  PARALLEL_MAKE = ""
>  CCACHE = ""
>  
> -SRC_URI[md5sum] = "c95d08fd5d93df0c11a2e1bdf0e01e0b"
> -SRC_URI[sha256sum] = "7c71c9650c65b715356547e20ca2dbe6313944278af8cc19c32a5337f46b181f"
> +SRC_URI[md5sum] = "5bddd02e2f82b62daa79f82717737a14"
> +SRC_URI[sha256sum] = "09ed31b4cc1f3c0411ef9a16eff79ef3b30d89c32ca46d5a01a41826c4ceb816"
> -- 
> 1.8.2
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-04-17 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 10:46 [meta-oe][PATCHv2 1/2] net-snmp: fix failure when starting on system without pci bus Jack Mitchell
2013-04-17 10:46 ` [meta-oe][PATCHv2 2/2] net-snmp: Update to 5.7.2 Jack Mitchell
2013-04-17 11:10   ` Martin Jansa [this message]
2013-04-17 11:18     ` Jack Mitchell
2013-04-17 11:09 ` [meta-oe][PATCHv2 1/2] net-snmp: fix failure when starting on system without pci bus Jack Mitchell

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=20130417111042.GF26007@jama \
    --to=martin.jansa@gmail.com \
    --cc=jack.mitchell@dbbroadcast.co.uk \
    --cc=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.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