From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] dpkg-base: Remove newly deployed debs from buildchroots
Date: Sun, 23 Aug 2020 18:30:37 +0200 [thread overview]
Message-ID: <20200823163037.GC11779@yssyq.m.ilbers.de> (raw)
In-Reply-To: <392163c4-00a2-3462-0f3e-dda06c22a656@siemens.com>
On Tue, Aug 18, 2020 at 07:57:26AM +0200, Jan Kiszka wrote:
> > Yes, Debian Policy section 3.2 requires that different packages have different
> > version numbers. Maybe we should introduce a script that would do that for the
> > developer.
>
> This won't help in the cases you play with a recipe, change small
> details, rebuild, test. It's reasonable to update the version when
> publishing. However, it's a needless burden to do that for a local
> development cycle. Here, Isar shall support that the just built instance
> of a package is also used locally, without an explicit "clean".
If this is how the upstream tooling works (which is a requirement for them
since there is no other way), things will get complicated and keep breaking. An
alternative could be to automate version bumping by requiring a local commit.
In the long term, I don't see a way around that.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-08-23 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 7:05 Jan Kiszka
2020-08-11 7:47 ` Harald Seiler
2020-08-17 12:50 ` Henning Schild
2020-08-17 15:38 ` Jan Kiszka
2020-08-17 17:21 ` Henning Schild
2020-08-18 5:53 ` Jan Kiszka
2020-08-17 19:27 ` Baurzhan Ismagulov
2020-08-18 5:57 ` Jan Kiszka
2020-08-23 16:30 ` Baurzhan Ismagulov [this message]
2020-08-24 7:17 ` Jan Kiszka
2020-08-23 16:06 ` Baurzhan Ismagulov
2020-08-24 7:16 ` Jan Kiszka
2020-09-21 19:17 ` Jan Kiszka
2020-10-28 13:39 ` Kanagarajan, Vijaikumar
2020-10-28 13:52 ` Jan Kiszka
2020-10-28 14:20 ` Kanagarajan, Vijaikumar
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=20200823163037.GC11779@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