From: chombourger@gmail.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/3] dpkg-base: Add dependecies between Isar recipes
Date: Tue, 6 Feb 2018 02:10:26 -0800 (PST) [thread overview]
Message-ID: <2ba52b0a-d97d-4a96-bb28-ce9d71ce5ff6@googlegroups.com> (raw)
In-Reply-To: <1b94801e-1d30-30ba-41c4-a68af606dd2d@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1174 bytes --]
+1 - this would allow us to remove one more local patch from our isar-based
project :)
On Monday, February 5, 2018 at 8:40:08 PM UTC+1, Jan Kiszka wrote:
>
> On 2018-01-25 09:38, Alexander Smirnov wrote:
> > Signed-off-by: Alexander Smirnov <asmi...@ilbers.de <javascript:>>
> > ---
> > meta/classes/dpkg-base.bbclass | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/meta/classes/dpkg-base.bbclass
> b/meta/classes/dpkg-base.bbclass
> > index 4941f9b..568d847 100644
> > --- a/meta/classes/dpkg-base.bbclass
> > +++ b/meta/classes/dpkg-base.bbclass
> > @@ -4,6 +4,10 @@
> > # Add dependency from buildchroot creation
> > do_build[depends] = "buildchroot:do_build"
> >
> > +# Add dependency between Isar recipes
> > +DEPENDS ?= ""
> > +do_build[deptask] = "do_deploy_deb"
> > +
> > # Each package should have its own unique build folder, so use
> > # recipe name as identifier
> > PP = "/home/builder/${PN}"
> >
>
> Please don't forget to merge this useful patch soon so that DEPENDS
> works properly.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
[-- Attachment #1.2: Type: text/html, Size: 1732 bytes --]
next prev parent reply other threads:[~2018-02-06 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 8:38 [PATCH 0/3] Implement hello <-> libhello pattern Alexander Smirnov
2018-01-25 8:38 ` [PATCH 1/3] dpkg-base: Add dependecies between Isar recipes Alexander Smirnov
2018-02-05 19:40 ` Jan Kiszka
2018-02-06 10:10 ` chombourger [this message]
2018-02-06 20:25 ` Alexander Smirnov
2018-01-25 8:38 ` [PATCH 2/3] build.sh: Install newly built packages Alexander Smirnov
2018-01-31 19:39 ` Jan Kiszka
2018-01-31 19:55 ` Alexander Smirnov
2018-01-31 20:01 ` Jan Kiszka
2018-02-01 7:49 ` Benedikt Niedermayr
2018-02-01 8:07 ` Alexander Smirnov
2018-02-01 10:09 ` Benedikt Niedermayr
2018-02-01 11:37 ` Jan Kiszka
2018-01-25 8:38 ` [PATCH 3/3] libhello: Add libhello Alexander Smirnov
2018-01-25 9:01 ` Jan Kiszka
2018-01-25 10:11 ` Alexander Smirnov
2018-01-25 10:30 ` Jan Kiszka
2018-01-29 16:14 ` [PATCH 0/3] Implement hello <-> libhello pattern Henning Schild
2018-02-05 21:56 ` Baurzhan Ismagulov
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=2ba52b0a-d97d-4a96-bb28-ce9d71ce5ff6@googlegroups.com \
--to=chombourger@gmail.com \
--cc=isar-users@googlegroups.com \
/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