From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: https://github.com/ilbers/hello conflicts with upstream hello
Date: Fri, 18 Jan 2019 10:05:23 +0100 [thread overview]
Message-ID: <20190118100523.43b9fd91@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190117165440.GL12226@yssyq.m.ilbers.de>
Am Thu, 17 Jan 2019 17:54:40 +0100
schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> On Thu, Jan 17, 2019 at 05:10:02PM +0100, Henning Schild wrote:
> > Yes, but conflicts that are known are mentioned in the metadata.
> > (debian/control)
> > So apt sees it before dpkg unpacks it and finds it.
>
> Conflicts: isn't the only way to handle various kinds of
> interoperability problems that arise in a large distribution like
> Debian. There are also diversions, which allow installing packages
> with conflicting files by renaming them in a controlled way after
> installation.
>
>
> > I just sent a series that shows the problem. You can also see it if
> > you IMAGE_INSTALL=example-hello and IMAGE_PREINSTALL=hello
>
> I see, thanks.
>
> I think we should use this opportunity to also rename the source
> package to hello-isar to avoid conflicts with apt-get source hello.
In that case is might also be a good idea to align the PN with the
changed name. hello -> hello-isar and example-hello > hello-isar
> > That or the metadata should know about the conflict. We can not
> > change upstream metadata, maybe one side is good enough.
>
> Conflicts: on the Isar side would be enough to make the packages
> incompatible, but apt-get installing example-hello after hello would
> fail.
>
>
> > One way or another. My series adds the feature to rebuild an
> > upstream package, and hello is a very good example for that. A
> > conflict would mean we could not test example-hello and hello in
> > the same image, so avoiding the conflict will be useful for that
> > case and not overkill.
>
> I agree that using upstream hello would be nice. An alternative could
> be building e.g. arc for the time being. In parallel, Maxim has
> started fixing example-hello. I'd prefer merging your code without
> breaking example-hello.
I am not in a hurry with that being merged. We could just drop the
patch that currently removes example-hello from the build, after the
renaming is done.
Henning
>
> With kind regards,
> Baurzhan.
>
prev parent reply other threads:[~2019-01-18 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:03 Henning Schild
2019-01-17 15:28 ` Baurzhan Ismagulov
2019-01-17 16:10 ` Henning Schild
2019-01-17 16:54 ` Baurzhan Ismagulov
2019-01-18 9:05 ` Henning Schild [this message]
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=20190118100523.43b9fd91@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=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