From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-ivi] [PATCHv2] connman: do not delete init scripts in bbappend
Date: Wed, 3 Jul 2013 14:31:16 +0200 [thread overview]
Message-ID: <20130703123116.GA3452@jama> (raw)
In-Reply-To: <CAJTo0LagT0i=JkkxEkd1mPbNH-F17vV9z4Pw9-bf8yNAUE0XHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Wed, Jul 03, 2013 at 01:09:47PM +0100, Burton, Ross wrote:
> In that case, you can delete INITSCRIPT_NAME and INITSCRIPT_PARAMS too
> surely. Then all you're left is the PRINC, so you can delete that if
> you don't care/are using the PR service, or delete that bbappend when
> connman 1.16 is integrated.
Using PR service isn't enough to keep binary feed sane after removing
PRINC.
PR service bumps least significant number in PKGR value. PRINC bumps
most significant (even from INC_PR when used).
INC_PR = "r1"
PR = "${INC_PR}.1"
PRINC := "${@int(PRINC) + 1}"
EXTENDPRAUTO = ".1"
PKGR = "r2.1.1"
After removing PRINC, EXTENDPRAUTO is bumped, but still PKGR is lower:
PKGR = "r1.1.2"
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-07-03 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 11:28 [meta-ivi] [PATCH] connman: delete init scripts if 'sysvinit' feature is enabled Sergey Matyukevich
2013-07-03 11:36 ` Burton, Ross
2013-07-03 11:59 ` [meta-ivi] [PATCHv2] connman: do not delete init scripts in bbappend Sergey Matyukevich
2013-07-03 12:09 ` Burton, Ross
2013-07-03 12:31 ` Martin Jansa [this message]
2013-07-03 12:38 ` Behrens, Holger
2013-07-03 16:13 ` Sergey Matyukevich
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=20130703123116.GA3452@jama \
--to=martin.jansa@gmail.com \
--cc=ross.burton@intel.com \
--cc=yocto@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.