From: Baurzhan Ismagulov <ibr@radix50.net>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] Add support for supplying more types of debian package relationships
Date: Tue, 15 Oct 2019 12:38:46 +0200 [thread overview]
Message-ID: <20191015103846.ikzksd4rby34fk4q@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20191014190100.329e37e5@md1za8fc.ad001.siemens.net>
On Mon, Oct 14, 2019 at 07:01:00PM +0200, Henning Schild wrote:
> My suggestion here is to keep that patch in your layer. You having that
> problem 20 times does not make it common, 20 independent users would ;).
>
> So you could put that magic into a dpkg-my-layer-yocto-glue class. The
> deps in Isar are a pain, because we are dealing with two worlds. I
> personally do not think that "pretending this away" is a good idea.
>
> If you actually have configure + compile tasks in your dpkg-raw you are
> on the wrong track and should stop pretending its yocto! Or at least
> make sure all that gets done in buildchroot. If you want please explain
> what you are doing, like Jan asked before.
People use this feature and ask for various corner cases. If we can cover those
till proper dependency support is implemented (which would probably require
modifying bitbake or developing a different tool), I'd like to apply the patch
because it helps users today.
Konstantinos, do you see a possibility to document this and provide a test
case?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-10-15 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 8:41 Dalamagkidis, Konstantinos
2019-09-11 8:57 ` Jan Kiszka
2019-09-11 9:02 ` Jan Kiszka
2019-09-11 9:32 ` Dalamagkidis, Konstantinos
2019-10-14 17:01 ` Henning Schild
2019-10-15 10:38 ` Baurzhan Ismagulov [this message]
2019-09-13 8:32 ` Baurzhan Ismagulov
2019-10-14 16:49 ` Henning Schild
2019-09-17 9:07 ` Henning Schild
2019-10-08 11:01 ` Baurzhan Ismagulov
2019-10-08 11:26 ` Jan Kiszka
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=20191015103846.ikzksd4rby34fk4q@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