From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta-isar: hello: Use <orig-version> in CHANGELOG_V
Date: Mon, 8 Jun 2020 09:59:13 +0200 [thread overview]
Message-ID: <3f93909a-e901-549c-d5da-199cee8cdd1a@siemens.com> (raw)
In-Reply-To: <20200606083742.GF5077@yssyq.m.ilbers.de>
On 06.06.20 10:37, Baurzhan Ismagulov wrote:
> On Fri, Jun 05, 2020 at 07:55:50PM +0200, Jan Kiszka wrote:
>> Can we tell "apt-get source" which directory to create
>> (rather than <package-name>-<upstream-version>? Didn't find anything.
>
> I think it would unpack whatever has been packed. IIRC,
> <package-name>-<upstream-version> is required by the Debian Policy, and build
> tools would complain if it isn't the case. Possibly that is just a warning and
> might be forceable.
>
> If the goal is to encode the version into the package name, the usual Debian
> way is doing that without the dash (libqtwebkit4, libqt5webkit5, ges1.0-tools).
The goal is to provide ${S} without knowing <upstream-version>. Or can
we adjust ${S} in do_apt_fetch so that all succeeding task will see that?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-06-08 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:29 Jan Kiszka
2020-04-28 16:00 ` Henning Schild
2020-04-28 16:01 ` Jan Kiszka
2020-04-29 5:54 ` Henning Schild
2020-04-29 6:10 ` Jan Kiszka
2020-04-29 6:27 ` Henning Schild
2020-04-29 6:37 ` Henning Schild
2020-04-29 6:51 ` Henning Schild
2020-06-05 17:46 ` Henning Schild
2020-06-05 17:55 ` Jan Kiszka
2020-06-06 8:10 ` Henning Schild
2020-06-06 8:37 ` Baurzhan Ismagulov
2020-06-08 7:59 ` Jan Kiszka [this message]
2020-05-07 20:09 ` Baurzhan Ismagulov
2020-05-08 6:05 ` Jan Kiszka
2020-05-08 6:13 ` Baurzhan Ismagulov
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=3f93909a-e901-549c-d5da-199cee8cdd1a@siemens.com \
--to=jan.kiszka@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