From: Baurzhan Ismagulov <ibr@radix50.net>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] Add support for supplying more types of debian package relationships
Date: Fri, 13 Sep 2019 10:32:21 +0200 [thread overview]
Message-ID: <20190913083221.GK6062@yssyq.m.ilbers.de> (raw)
In-Reply-To: <e054cb14-2d05-647e-ed71-e89291482300@siemens.com>
On Wed, Sep 11, 2019 at 10:57:34AM +0200, Jan Kiszka wrote:
> One of the thing to consider while designing & enhancing the recipe API for
> debianize: We should not create something that is as complex as writing
> Debian control files directly - or even more complex than that.
This is exactly the point. In my experience, new users tend to shy away from
debianizing their applications, presumably because debhelper documentation is
somewhat complicated -- at least I spent more time with the docs than with
actual debianizing. So, people are tempted to use quick solutions, and my
impression is that debianize.bbclass is a good helper here. It will get
complicated as we cover more use cases, and using tons of variables to control
the configuration is as simple as we can get it. We should gather experience
with that, but I think it will still have its value as first debianizing aid.
After one is past that step, we should recommend moving the debian control
files from meta to the application in the manual.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-09-13 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 8:41 Dalamagkidis, Konstantinos
2019-09-11 8:57 ` Jan Kiszka
2019-09-11 9:02 ` Jan Kiszka
2019-09-11 9:32 ` Dalamagkidis, Konstantinos
2019-10-14 17:01 ` Henning Schild
2019-10-15 10:38 ` Baurzhan Ismagulov
2019-09-13 8:32 ` Baurzhan Ismagulov [this message]
2019-10-14 16:49 ` Henning Schild
2019-09-17 9:07 ` Henning Schild
2019-10-08 11:01 ` Baurzhan Ismagulov
2019-10-08 11:26 ` Jan Kiszka
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=20190913083221.GK6062@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