public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] Add support for specifying package architecture using DPKG_ARCH
Date: Mon, 7 Oct 2019 12:39:21 +0200	[thread overview]
Message-ID: <20191007103921.77p7mjkpn3pijmhy@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20191007102042.wovptj4eagg4gqoj@yssyq.m.ilbers.de>

Looking at dpkg-buildpackage(1), I see:

       -g     Equivalent to --build=source,all (since dpkg 1.17.11).

       -G     Equivalent to --build=source,any (since dpkg 1.17.11).

       -b     Equivalent to --build=binary or --build=any,all.

       -B     Equivalent to --build=any.

       -A     Equivalent to --build=all.

       -S     Equivalent to --build=source.

       -F     Equivalent    to    --build=full,    --build=source,binary    or
              --build=source,any,all (since dpkg 1.15.8).

So, the mechanism seems to be there. The question is how to split the
processing into two steps and tell bitbake to build the "all" part once.

With kind regards,
Baurzhan.


On Mon, Oct 07, 2019 at 12:20:42PM +0200, Baurzhan Ismagulov wrote:
> Debian should have the issue as well. I suppose, in Debian currently the last
> one wins, which should be fine with correct packaging. In that case, reducing
> the number of builds would be a welcome optimization. "Architecture-independent
> packages that can only be generated on one architecture" in [1] goes even
> further.
> 
> 1. https://wiki.ubuntu.com/MultiarchSpec

  reply	other threads:[~2019-10-07 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  8:41 Dalamagkidis, Konstantinos
2019-09-30  6:07 ` Jan Kiszka
2019-10-07 10:20   ` Baurzhan Ismagulov
2019-10-07 10:39     ` Baurzhan Ismagulov [this message]
2019-10-08 11:25       ` Jan Kiszka
2019-10-07 10:21 ` 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=20191007103921.77p7mjkpn3pijmhy@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --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