From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package for Gnome NetworkManager
Date: Fri, 2 Dec 2011 13:06:05 +0100 [thread overview]
Message-ID: <20111202130605.6f745c5a@skate> (raw)
In-Reply-To: <4ED8BEB1.50500@gmail.com>
Le Fri, 02 Dec 2011 13:04:01 +0100,
Daniel Mack <zonque@gmail.com> a ?crit :
> :) See the other thread. I solved it with a rmdir || echo "" for now,
> not to rely on the host's mkdir to have that particular feature.
It's already used in quite a few places in Buildroot:
$ git grep ignore-fail-on
package/hwdata/hwdata.mk: rmdir --ignore-fail-on-non-empty $(TARGET_DIR)/usr/share
package/libglib2/libglib2.mk: rmdir --ignore-fail-on-non-empty $(TARGET_DIR)/usr/share/glib-2.0
package/libglib2/libglib2.mk: rmdir --ignore-fail-on-non-empty $(TARGET_DIR)/usr/share/glib-2.0
package/logrotate/logrotate.mk: rmdir --ignore-fail-on-non-empty $(TARGET_DIR)/etc/logrotate.d
package/tinyhttpd/tinyhttpd.mk: @rmdir --ignore-fail-on-non-empty $(TARGET_DIR)/var/www
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-12-02 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 11:14 [Buildroot] [PATCH] Add package for Gnome NetworkManager Daniel Mack
2011-12-02 11:18 ` Daniel Mack
2011-12-02 11:45 ` Thomas De Schampheleire
2011-12-02 11:52 ` Daniel Mack
2011-12-02 11:56 ` Thomas De Schampheleire
2011-12-02 11:59 ` Daniel Mack
2011-12-02 12:00 ` Thomas Petazzoni
2011-12-02 12:04 ` Daniel Mack
2011-12-02 12:06 ` Thomas Petazzoni [this message]
2011-12-02 12:09 ` Daniel Mack
2011-12-02 12:13 ` [Buildroot] [PATCH v3] " Daniel Mack
2012-01-02 13:57 ` Peter Korsgaard
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=20111202130605.6f745c5a@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox