All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] a philosophical question about Config.in and "comment" directives
Date: Fri, 17 Apr 2015 18:35:18 +0200	[thread overview]
Message-ID: <20150417163518.GC5271@free.fr> (raw)
In-Reply-To: <55313266.9000600@mind.be>

Arnout, All,

On 2015-04-17 18:18 +0200, Arnout Vandecappelle spake thusly:
> On 17/04/15 17:00, Yann E. MORIN wrote:
> > Rovert, All,

Damn, my keyboard skills really need to be improved upon... :-/
Sorry, Robert...

> > On 2015-04-17 08:58 -0400, Robert P. J. Day spake thusly:
[--SNIP--]
> > Well, you are right that "it would make moere sense" from a theoretical
> > point of view, and that there is no functional difference. BTW, there
> > are other  such architectural options, like MMU, that we handle the same
> > way as well.

> > Just a side note: I personally find it easier to read the way we have it
> > now: having the "depends on" directly in the package dependency list
> > looks more obvious to me (but hey! I'm kind of a weirdo! ;-) 
> 
>  Well, then either your first statement that it makes more sense was not true,
> or else you don't make sense :-P

Well, I never I did make sense in my head! ;-)

Seriously: enclosing the whole file inside a big architectural
dependency does make sense at a technical level. But I don;t grok it as
easily as it is now.

I.e. a car is far safer than a motorbike from a technical point of view
(it has airbags and safety-belts, can not easily slide on its side with
driver stuck between it and the asphalt, is warm in winter and has A/C
in summer...). But I'll use my motorbike because I prefer it. ;-)

>  Note that I also think it makes more sense to have the comment at the top then
> at the bottom.

So do I. At least, we can agree on that! hehe! ;-)
 
Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2015-04-17 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 12:58 [Buildroot] a philosophical question about Config.in and "comment" directives Robert P. J. Day
2015-04-17 15:00 ` Yann E. MORIN
2015-04-17 16:18   ` Arnout Vandecappelle
2015-04-17 16:28     ` Robert P. J. Day
2015-04-17 16:35     ` Yann E. MORIN [this message]
2015-04-20 19:19     ` Peter Korsgaard
2015-04-20 19:29       ` Robert P. J. Day

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=20150417163518.GC5271@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.