From: Alexander Smirnov <asmirnov@ilbers.de>
To: Claudius Heine <ch@denx.de>,
claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH v4 1/5] implement isar-bootstrap using debootstrap
Date: Wed, 14 Mar 2018 13:38:07 +0300 [thread overview]
Message-ID: <a27c4339-0bff-112b-e299-6ccec646a487@ilbers.de> (raw)
In-Reply-To: <1521021141.16621.86.camel@denx.de>
On 03/14/2018 12:52 PM, Claudius Heine wrote:
> Hi Alex,
>
> On Wed, 2018-03-14 at 11:56 +0300, Alexander Smirnov wrote:
>> On 03/07/2018 07:44 PM, claudius.heine.ext@siemens.com wrote:
>>> From: Claudius Heine <ch@denx.de>
>>>
>>> Since multistrap is deprecated for some years, it is required to
>>> change
>>> to debootstrap.
>>>
>>> This patch introduces the 'isar-bootstrap' recipe that implement
>>> the
>>> creation of a minimal base root file system using debootstrap.
>>>
>>
>> Why do you use term 'bootstrap'? It's completely different topic
>> than
>> debootstrap.
>
> Because I want to be implementation independent. If for some reason
> someone wants to change the name of the tool again (I know its not to
> be expected), this way only the implementation of the isar-bootstrap
> needs to be changed.
> In theory with an alternative implementation of some interfaces other
> distribution could be supported. I don't know in which direction isar
> will go, but binding your interface names to tightly to the name of
> some third-party products is not a good idea.
>
> What I tried is called loose coupling and that is generally seen as a
> good software design pattern.
>
>> According to the wiki:
>>
>> https://wiki.debian.org/DebianBootstrap#Bootstrapping
>>
>> Bootstraping is a process of creation Debian from zero to a full
>> archive.
>
> The word "bootstrapping" is used in many projects and generally
> describes starting something from almost nothing. Also this patchset
> doesn't use "DebianBootstrap" is uses "isar-bootstrap".
In this case just do not use terms from Debian world. It would be enough
to name it like 'base-rootfs'. That's for example, how 'buildchroot'
term was invented, to avoid intersections with 'sysroot' and 'buildroot'.
AFAIK there are 2 kinds opinions in Debian community about bootstraping:
- Build from sources (DebianBootstrap, rebootstrap)
- Install from debs (debootstrap)
My question, why it's so important to use initially ambiguous term,
which may lead to potential confusing for Debian users?
Alex
next prev parent reply other threads:[~2018-03-14 10:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 16:44 [PATCH v4 0/5] Debootstrap integration claudius.heine.ext
2018-03-07 16:44 ` [PATCH v4 1/5] implement isar-bootstrap using debootstrap claudius.heine.ext
2018-03-08 7:53 ` Claudius Heine
2018-03-14 8:56 ` Alexander Smirnov
2018-03-14 9:52 ` Claudius Heine
2018-03-14 10:38 ` Alexander Smirnov [this message]
2018-03-14 14:14 ` Claudius Heine
2018-03-14 14:25 ` Alexander Smirnov
2018-03-14 18:53 ` Jan Kiszka
2018-03-15 8:05 ` Claudius Heine
2018-03-15 8:58 ` Alexander Smirnov
2018-03-15 22:07 ` Claudius Heine
2018-03-16 5:49 ` Alexander Smirnov
2018-03-28 6:00 ` Jan Kiszka
2018-03-14 14:04 ` Alexander Smirnov
2018-03-14 14:26 ` Claudius Heine
2018-03-14 14:35 ` Alexander Smirnov
2018-03-14 16:13 ` Claudius Heine
2018-03-07 16:44 ` [PATCH v4 2/5] meta/isar-bootstrap-helper.bbclass: handle rfs customization centrally claudius.heine.ext
2018-03-07 16:44 ` [PATCH v4 3/5] meta/buildchroot: switch to using isar-bootstrap claudius.heine.ext
2018-03-08 8:18 ` Claudius Heine
2018-03-07 16:44 ` [PATCH v4 4/5] meta-isar/isar-image-base: " claudius.heine.ext
2018-03-07 16:44 ` [PATCH v4 5/5] meta-isar/multiconfig: remove multistrap references claudius.heine.ext
2018-03-07 19:51 ` [PATCH v4 0/5] Debootstrap integration Jan Kiszka
2018-03-08 6:06 ` Jan Kiszka
2018-03-08 8:14 ` Claudius Heine
2018-03-09 14:22 ` 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=a27c4339-0bff-112b-e299-6ccec646a487@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@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