All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: fix potential entire root filesystem removal
Date: Thu, 15 Sep 2016 21:20:15 +0200	[thread overview]
Message-ID: <20160915212015.761725b7@free-electrons.com> (raw)
In-Reply-To: <aee7cccd-eb3a-d376-99b0-a9ba3cb950b2@mind.be>

Hello,

On Thu, 15 Sep 2016 18:19:01 +0200, Arnout Vandecappelle wrote:

>  I'm sure I had a reason to add the /*, but I can't remember and the commit
> message isn't helpful. The only difference (except for keeping the directory)
> that I can think of is that .stamp files are kept, but (a) they should be
> removed and (b) there aren't any stamp files in that directory...

I don't really see a reason for the /*, and it seems really dangerous :)

> [snip]
> >  # Normal handling of downloaded toolchain tarball extraction.
> > -ifneq ($(TOOLCHAIN_EXTERNAL_SOURCE),)
> > +ifeq ($(BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD),y)  
> 
>  You've just made these two equivalent again. But it's better like that.

Absolutely. But I believe the $(BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD),y test
is clearer and less likely to get broken.

> >  TOOLCHAIN_EXTERNAL_EXCLUDES = usr/lib/locale/*  
> 
>  I thought: hey, this can't be right, TOOLCHAIN_EXTERNAL_EXCLUDES should still
> be set for non-downloaded toolchains that do have a source. But since those
> don't exist, it doesn't matter.

When a toolchain is not downloaded, it is also not extracted: it is
also there somewhere on the filesystem. So there's nothing to exclude
when extracting, since we're not extracting.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-15 19:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15  8:58 [Buildroot] [PATCH] toolchain-external: fix potential entire root filesystem removal Thomas Petazzoni
2016-09-15 10:04 ` Peter Korsgaard
2016-09-15 16:35   ` Arnout Vandecappelle
2016-09-15 20:07     ` Peter Korsgaard
2016-09-15 20:58       ` Arnout Vandecappelle
2016-09-15 21:21         ` Peter Korsgaard
2016-09-16  7:42           ` [Buildroot] CMAKE_SYSROOT issue [was: Re: [PATCH] toolchain-external: fix potential entire root filesystem removal] Arnout Vandecappelle
2016-09-16  8:52             ` Peter Korsgaard
2016-09-21 19:26               ` Yann E. MORIN
2016-09-21 21:55                 ` Peter Korsgaard
2016-09-15 19:22   ` [Buildroot] [PATCH] toolchain-external: fix potential entire root filesystem removal Thomas Petazzoni
2016-09-15 20:08     ` Peter Korsgaard
2016-09-15 16:19 ` Arnout Vandecappelle
2016-09-15 19:20   ` Thomas Petazzoni [this message]
2016-09-16 10:13     ` Mason

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=20160915212015.761725b7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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.