From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] buildchroot: Allow downgrades when installing packages
Date: Mon, 4 Mar 2019 10:08:12 +0100 [thread overview]
Message-ID: <370fe667-e8cc-48ec-5410-9e76c05d9826@siemens.com> (raw)
In-Reply-To: <c91bfe2b-e84f-f6f0-2d2a-a24c306e0212@siemens.com>
On 04.03.19 10:04, [ext] Claudius Heine wrote:
> Hi Jan,
>
> On 23/02/2019 11.44, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This can happen when changing the recipe of a self-built package, and
>> that already when going from v1.0-rc3 to v1.0.
>
> So the issue is that the buildchroot is reused for each recipe/package and if a
> newer one was once installed, it will not be removed. Right?
>
> Then why not use a copy of the buildchroot for each recipe?
>
> That way missing dependencies would also be found more easily.
Yes, that is the future direction (post-0.7), possibly achieved by switching to
sbuilder. For now, we need to deal with the shared buildchroot.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-03-04 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 10:44 Jan Kiszka
2019-02-25 9:39 ` Henning Schild
2019-02-25 9:57 ` Jan Kiszka
2019-02-25 10:15 ` Henning Schild
2019-02-25 11:08 ` Jan Kiszka
2019-03-19 10:10 ` Baurzhan Ismagulov
2019-03-19 10:31 ` Jan Kiszka
2019-03-19 17:33 ` Maxim Yu. Osipov
2019-03-19 18:46 ` Jan Kiszka
2019-03-04 9:04 ` Claudius Heine
2019-03-04 9:08 ` Jan Kiszka [this message]
2019-03-28 12:42 ` Maxim Yu. Osipov
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=370fe667-e8cc-48ec-5410-9e76c05d9826@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.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