From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
Henning Schild <henning.schild@siemens.com>,
isar-users@googlegroups.com
Cc: Christian Storm <christian.storm@siemens.com>
Subject: Re: [PATCH] dpkg-raw: take unmodified DEBIAN_DEPENDS for the package
Date: Wed, 31 Jan 2018 15:56:36 +0100 [thread overview]
Message-ID: <65ac4abd-eef1-bd6a-1cab-63bd1476e50a@siemens.com> (raw)
In-Reply-To: <4991ec01-e369-f30f-14bd-ba14807881e1@ilbers.de>
Hi,
On 01/11/2018 12:42 PM, Alexander Smirnov wrote:
> On 12/14/2017 08:36 PM, Henning Schild wrote:
>> To express advanced debian dependencies version numbers in brackets and
>> other constructs are allowed. In such cases you would also have spaces
>> in DEBIAN_DEPENDS which can not just get replaced with commas. Doing
>> that will create invalid "Depends:"-lines.
>>
>> This patch just takes the string as found in the recipe. This way users
>> can express whatever they need and Isar does not need to know anything
>> about the semantics or syntax of that string.
>>
>> This change means that anyone using dpkg-raw will have to comma-separate
>> their DEBIAN_DEPENDS. The change breaks backwards compatibility but
>> simplifies things and hopefully prevents further problems in that space.
>>
>
> Applied to next, thanks!
>
I am now trying to convert my 'DEBIAN_DEPENDS' to the new format and I
found some issues doing it that way.
For instance if you are adding DEBAIN_DEPENDS inside a bbclass like this:
DEBIAN_DEPENDS += " \
jq, \
iptables, \
"
This results to the following entry in control file:
Depends: jq, iptables,
dpkg-deb does not seems to be happy with this.
That means that this patch in comparison the the one I submitted has
also the disadvantage of enforcing a less readable format in the recipe
file and expects special handling of the last ','.
So in the end, the complexity that we save here has to be spend
somewhere else.
Cheers,
Claudius
P.S.: My proposed patch needs a small change to handle tab characters
additional to spaces though.
--
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
prev parent reply other threads:[~2018-01-31 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 17:36 Henning Schild
2018-01-11 11:42 ` Alexander Smirnov
2018-01-31 14:56 ` Claudius Heine [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=65ac4abd-eef1-bd6a-1cab-63bd1476e50a@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=christian.storm@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