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] [PATCH 01/13 v6] support/scripts: add helper to hardlink-or-copy
Date: Sun, 8 May 2016 09:25:27 +0200	[thread overview]
Message-ID: <20160508072526.GA24011@free.fr> (raw)
In-Reply-To: <c09bf375-50ae-5e3d-77a1-4637c34bb888@mind.be>

Arnout, All,

On 2016-05-07 20:44 +0200, Arnout Vandecappelle spake thusly:
> On 05/06/16 00:38, Yann E. MORIN wrote:
> >Arnout, All,
> >
> >On 2016-05-04 00:53 +0200, Arnout Vandecappelle spake thusly:
> >>On 04/29/16 00:27, Yann E. MORIN wrote:
> [snip]
> >>>+# hardlink-or-copy -- helper script to first try to hardlink,
> >>>+# and fallback to copy.
> >>>+HARDLINK_OR_COPY := support/scripts/hardlink-or-copy
> >>
> >> = instead of :=
> >>
> >>
> >> However (and here starts the difference of opinion in coding style): why do
> >>you need to define a variable for this? In general, I'm not a big fan of
> >>variables that just contain a constant string. For numbers, it makes sense,
> >>because a number is meaningless by itself. But a string is already something
> >>that is searchable and identifiable. And in this specific case, the variable
> >>name is even the same as the value... So what's the point? OK, you save 13
> >>characters in every place where you use it (that's in only 2 (TWO) places,
> >>by the way).
> >>
> >> We do have a few existing cases of such variables, but IMHO they are
> >>equally useless. And mostly introduced by you, BTW :-)
> >
> >Well, when the thing s used in multiple places, I find it "better" to
> >use a variable so as to be able to change all locations at once with a
> >single edit (even if we don't plan on renaming or moving it).
> 
>  I was going to build a big argument about why I disagree, but I see in v7
> you already dropped the variable so let's leave it at that :-)

Out of curiosity, what's your argument against having such a variable?

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-05-08  7:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 22:27 [Buildroot] [PATCH 00/13 v6] legal-info improvements and completeness (branch yem/legal-3) Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 01/13 v6] support/scripts: add helper to hardlink-or-copy Yann E. MORIN
2016-05-03 22:53   ` Arnout Vandecappelle
2016-05-05 22:38     ` Yann E. MORIN
2016-05-07 18:44       ` Arnout Vandecappelle
2016-05-08  7:25         ` Yann E. MORIN [this message]
2016-04-28 22:27 ` [Buildroot] [PATCH 02/13 v6] core/legal-info: use the helper to install source archives Yann E. MORIN
2016-05-03 22:57   ` Arnout Vandecappelle
2016-05-05 22:44     ` Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 03/13 v6] core/pkg-generic: reorder variables definitions for legal-info Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 04/13 v6] core/legal-info: ensure legal-info works in off-line mode Yann E. MORIN
2016-05-03 23:13   ` Arnout Vandecappelle
2016-04-28 22:27 ` [Buildroot] [PATCH 05/13 v6] core/pkg-generic: add variable to store the package rawname-version Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 06/13 v6] core/legal-info: install source archives in their own sub-dir Yann E. MORIN
2016-05-03 23:14   ` Arnout Vandecappelle
2016-05-05 22:55     ` Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 07/13 v6] core/legal-info: add package version to license directory Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 08/13 v6] core/apply-patches: store full path of applied patches Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 09/13 v6] core/legal-info: also save patches Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 10/13 v6] support/apply-patches: bail-out on duplicate patch basenames Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 11/13 v6] core/legal-info: also save extra downloads Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 12/13 v6] core/legal-info: generate a hash of all saved files Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 13/13 v6] legal-info: explicitly state how patches are licensed Yann E. MORIN
2016-05-03 22:34   ` Arnout Vandecappelle
2016-05-03 22:33 ` [Buildroot] [PATCH 00/13 v6] legal-info improvements and completeness (branch yem/legal-3) Arnout Vandecappelle
2016-05-05 22:01   ` Yann E. MORIN

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=20160508072526.GA24011@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.