From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
"[ext] Henning Schild" <henning.schild@siemens.com>,
isar-users@googlegroups.com
Cc: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>,
Christian Storm <christian.storm@siemens.com>,
Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 5/6] meta/dpkg: add dpkg-custom class
Date: Mon, 11 Sep 2017 11:39:38 +0300 [thread overview]
Message-ID: <fdc25561-c559-239e-6802-5cbc97ac6b9d@ilbers.de> (raw)
In-Reply-To: <4ea25dde-acf8-f8e7-1153-9c33cabef4e3@siemens.com>
Drop the unrelated stuff...
>> Also not a big fan of this name. 'custom' is a bit too unspecific for
>> what it does. I get that your idea that those packages are *custom*
>> made, but at the same time, so are all the packages that are directly
>> created within isar.
>>
>> I liked the old 'dpkg-bin' name more, but maybe even this is a bit to
>> unspecific. How about 'dpkg-plain'? That describes better that those
>> packages are very simple, created impromptu without much to it, IMO.
>
> How about dpkg-wrap, because this wraps existing stuff as-is into debian
> package?
>
Eventually Isar will have three ways to create Debian package:
- Build it in chroot (current dpkg.bbclass)
- Build package using cross-compilation (planned to be dpkg-cross.bbclass)
- Pack existing files (current dpkg-custom.bbclass)
I agree with Jan, that custom is very wide term. Customization usually
means modifying something existing according to your needs. In current
patch you create your own package from the scratch, so there is no
reference package for them from which you have branched and which you
have customized.
Due to we have several classes to create package, I'd suggest to use the
words that describe *how* this class build package. So, dpkg-wrap,
dpkg-pack etc...
--
With best regards,
Alexander Smirnov
ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2017-09-11 8:39 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 19:03 [PATCH 0/6] v3 of getting the custom debian package in Henning Schild
2017-08-30 19:03 ` [PATCH 1/6] meta/dpkg: Make 'do_unpack' more generic, prepare for pulling out Henning Schild
2017-09-04 15:11 ` Alexander Smirnov
2017-09-04 16:47 ` Jan Kiszka
2017-09-05 7:05 ` Claudius Heine
2017-09-05 7:25 ` Alexander Smirnov
2017-09-05 7:37 ` Alexander Smirnov
2017-09-05 7:56 ` Claudius Heine
2017-09-08 8:30 ` Henning Schild
2017-09-08 8:44 ` Claudius Heine
2017-09-08 9:03 ` Henning Schild
2017-08-30 19:03 ` [PATCH 2/6] meta: Move 'do_fetch' and 'do_unpack' to base-class Henning Schild
2017-09-04 15:14 ` Alexander Smirnov
2017-09-04 16:03 ` Jan Kiszka
2017-09-04 16:10 ` Alexander Smirnov
2017-09-04 16:11 ` Jan Kiszka
2017-09-04 16:39 ` Alexander Smirnov
2017-09-04 16:45 ` Jan Kiszka
2017-08-30 19:03 ` [PATCH 3/6] meta/dpkg: rename to dpkg-debian and add comment Henning Schild
2017-08-31 8:23 ` Claudius Heine
2017-09-04 15:17 ` Alexander Smirnov
2017-09-04 16:05 ` Jan Kiszka
2017-08-30 19:03 ` [PATCH 4/6] meta/dpkg-debian: Make 'do_install' more generic, prepare for pulling out Henning Schild
2017-08-30 19:09 ` Henning Schild
2017-09-08 8:35 ` Henning Schild
2017-08-30 19:03 ` [PATCH 5/6] meta/dpkg: add dpkg-custom class Henning Schild
2017-08-31 8:38 ` Claudius Heine
2017-08-31 8:42 ` Jan Kiszka
2017-08-31 9:10 ` Claudius Heine
2017-08-31 9:32 ` Henning Schild
2017-08-31 12:14 ` Claudius Heine
2017-08-31 13:39 ` Henning Schild
2017-09-11 8:39 ` Alexander Smirnov [this message]
2017-08-31 8:53 ` Claudius Heine
2017-08-31 10:21 ` Henning Schild
2017-09-04 15:36 ` Alexander Smirnov
2017-09-04 16:08 ` Jan Kiszka
2017-09-04 16:30 ` Alexander Smirnov
2017-09-04 16:53 ` Jan Kiszka
2017-09-08 8:20 ` Henning Schild
2017-09-08 8:15 ` Henning Schild
2017-09-08 8:31 ` Alexander Smirnov
2017-09-08 8:42 ` Henning Schild
2017-09-08 8:50 ` Alexander Smirnov
2017-09-11 8:13 ` Claudius Heine
2017-09-11 8:19 ` Henning Schild
2017-09-11 9:12 ` Claudius Heine
2017-09-11 8:42 ` Claudius Heine
2017-08-30 19:03 ` [PATCH 6/6] recipes-app/example-custom: add example on how to use dpkg-custom Henning Schild
2017-09-04 15:40 ` Alexander Smirnov
2017-09-06 7:36 ` Henning Schild
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=fdc25561-c559-239e-6802-5cbc97ac6b9d@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=ch@denx.de \
--cc=christian.storm@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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