Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv4] core/pkg-generic: check proper package installation
Date: Mon, 9 Nov 2015 14:20:23 +0100	[thread overview]
Message-ID: <56409D97.20002@lucaceresoli.net> (raw)
In-Reply-To: <20151106230701.GC3746@free.fr>

Dear Yann,

Yann E. MORIN wrote:
> Arnout, All,
>
> On 2015-11-06 23:55 +0100, Arnout Vandecappelle spake thusly:
>> On 06-11-15 20:15, Yann E. MORIN wrote:
>>> Some packages misbehave, and install files in either of;
>>>    - $(STAGING_DIR)/$(O) or $(TARGET_DIR)/$(O),
>>>    - $(STAGING_DIR)/$(HOST_DIR) or $(TARGET_DIR)/$(HOST_DIR).
>>>
>>> One common reason for that is that pkgconf now prepends the sysroot path
>>> to all the paths it returns. Other reasons vary, but are mostly due to
>>> poorly writen generic-packages.
>>>
>>> Add a check for those locations, as part of the command blocks for the
>>> target and staging installs.
>>>
>>> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>>> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
>>> Cc: Arnout Vandecappelle <arnout@mind.be>
>>> Cc: Peter Seiderer <ps.report@gmx.net>
>>> Cc: Romain Naour <romain.naour@openwide.fr>
>>>
[...]
>>> +		exit 1; \
>>> +	fi
>>
>>   I think it's better without this duplication so with a second parameter and
>> calling the function twice.
>
> Well, it's either duplication of the if-block, or duplication of the
> call sites. And I think it is better to have duplication of the
> if-blocks, in cas we need to check for mor eloactions, otherwise we'd
> have to duplicate even more the call sites...

Is it possible to make check-install-dirs (note the plural) just call
multiple times check-install-dir (singular), passing a different path
each time?

I'm sure you know all problems in computer science (except one) can be
solved by adding another level of indirection! :-)

Obviously this can be a future improvement, especially useful in case
the list of paths to check grew longer.

-- 
Luca

  parent reply	other threads:[~2015-11-09 13:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 19:15 [Buildroot] [PATCHv4] core/pkg-generic: check proper package installation Yann E. MORIN
2015-11-06 22:55 ` Arnout Vandecappelle
2015-11-06 23:07   ` Yann E. MORIN
2015-11-06 23:12     ` Arnout Vandecappelle
2015-11-09 13:20     ` Luca Ceresoli [this message]
2015-11-09 14:52       ` Arnout Vandecappelle
2015-11-29 17:58 ` Thomas Petazzoni
2015-11-29 18:10   ` Yann E. MORIN
2015-11-29 18:27     ` Thomas Petazzoni
2015-11-29 20:04       ` Yann E. MORIN
2015-11-29 20:31       ` Arnout Vandecappelle

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=56409D97.20002@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox