From: Claudius Heine <ch@denx.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [RFC PATCH 0/1] Special debian depends entries
Date: Thu, 14 Dec 2017 15:52:18 +0100 [thread overview]
Message-ID: <1513263138.31110.37.camel@denx.de> (raw)
In-Reply-To: <20171214153628.1b3d6d36@mmd1pvb1c.ad001.siemens.net>
[-- Attachment #1: Type: text/plain, Size: 3453 bytes --]
On Thu, 2017-12-14 at 15:36 +0100, Henning Schild wrote:
> Am Thu, 14 Dec 2017 15:12:37 +0100
> schrieb Claudius Heine <ch@denx.de>:
>
> > Hi Henning,
> >
> > On Thu, 2017-12-14 at 14:42 +0100, Henning Schild wrote:
> > > Am Wed, 13 Dec 2017 17:07:09 +0100
> > > schrieb "[ext] claudius.heine.ext@siemens.com"
> > > <claudius.heine.ext@siemens.com>:
> > >
> > > > From: Claudius Heine <ch@denx.de>
> > > >
> > > > Hi,
> > > >
> > > > this patch is to start the discussion about how to implement
> > > > the
> > > > debian depends.
> > > >
> > > > Instead of going the just 'echo ${DEBIAN_DEPENDS}' route, I
> > > > chose
> > > > to
> > > > be backwards compatible. Another reason for this is also for
> > > > the
> > > > possible next feature where ISAR 'DEPENDS' or 'RDEPENDS' will
> > > > be
> > > > converted to the package specific 'DEBIAN_DEPENDS'.
> > >
> > > With the current nature of dpkg-raw DEPENDS and RDEPENDS make no
> > > sense.
> > > Maybe some day the class will do more than just wrap stuff in a
> > > package, but at the moment i do not see that coming.
> > > And even if that ever happened the class could take care of
> > > turning
> > > the
> > > bitbake-list (R)DEPENDS into a Debian comma-seperated list.
> > >
> > > I tried your code in a bash (not in Isar/bitbake etc.) and i got
> > > a
> > > few
> > > more commas that i would have expected.
> > >
> > > 'libc, (>=, 2.16)', 'tar, |, bsdtar', systemd
> > >
> > > Shell code is nasty, i think i do not even want to know why it
> > > worked for you or wether it would work in Isar with my build
> > > env.
> >
> > I works in here because the ${DEBIAN_DEPENDS} is inserted by
> > bitbake
> > before any shell is executed. So in shell code for this example
> > looks
> > like this:
> >
> > DEBIAN_DEPS="$(for i in 'libc (>= 2.16)' 'tar | bsdtar'
> > systemd;do
> > echo $i,;done|tr '\n' ' '|sed 's/, *$//')"
> >
> > If you try that out with your shell:
> >
> > $ echo "$(for i in 'libc (>= 2.16)' 'tar | bsdtar' systemd;do
> > echo
> > $i,;done|tr '\n' ' '|sed 's/, *$//')"
> > libc (>= 2.16), tar | bsdtar, systemd
> >
> > It works correctly just like in bitbake.
> >
> > DEBIAN_DEPENDS is not a shell variable but a bitbake one.
> >
> > But I get your point that this is confusing and error-prone. Doing
> > it
> > with python might be easier.
>
> It is just one of multiple points.
>
> Could you live with the simple solution of just taking the string
> from
> the recipe and requiring recipe-updates?
I would rather not break backward compatibility.
I know that isar is not at a stage were a fancy idea like this one
really matters, but for me this issue is currently not important enough
to justify this breakage and the work to change all the recipes relying
on the old behavior.
So for me we either fix it in a compatible way, like my patch does, or
don't bother and wait for a usecase where we cannot advice the user to
just debianize the sources in some way.
Cheers,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-14 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 16:07 claudius.heine.ext
2017-12-13 16:07 ` [RFC PATCH 1/1] meta/dpkg-raw: support for special debian package dependencies claudius.heine.ext
2017-12-14 13:42 ` [RFC PATCH 0/1] Special debian depends entries Henning Schild
2017-12-14 14:12 ` Claudius Heine
2017-12-14 14:36 ` Henning Schild
2017-12-14 14:52 ` Claudius Heine [this message]
2017-12-14 16:20 ` Henning Schild
2017-12-14 17:02 ` Claudius Heine
2017-12-14 17:31 ` Henning Schild
2017-12-15 8:24 ` Claudius Heine
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=1513263138.31110.37.camel@denx.de \
--to=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@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