From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bootstrap: remove development/debug files
Date: Mon, 12 Jan 2015 22:00:44 +0100 [thread overview]
Message-ID: <20150112220044.0db3d53b@free-electrons.com> (raw)
In-Reply-To: <1421094218-2999-1-git-send-email-yegorslists@googlemail.com>
Dear Yegor Yefremov,
On Mon, 12 Jan 2015 21:23:38 +0100, Yegor Yefremov wrote:
> *.min.* files are sufficient for a production system, so
> remove other files, that will be used during development
> stage.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> package/bootstrap/bootstrap.mk | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/package/bootstrap/bootstrap.mk b/package/bootstrap/bootstrap.mk
> index 1bf8aa2..f79a00f 100644
> --- a/package/bootstrap/bootstrap.mk
> +++ b/package/bootstrap/bootstrap.mk
> @@ -16,6 +16,11 @@ endef
> define BOOTSTRAP_INSTALL_TARGET_CMDS
> mkdir -p $(TARGET_DIR)/var/www/bootstrap
> cp -dpfr $(@D)/dist/* $(TARGET_DIR)/var/www/bootstrap
> +
> + rm $(TARGET_DIR)/var/www/bootstrap/css/bootstrap-theme.css*
> + rm $(TARGET_DIR)/var/www/bootstrap/css/bootstrap.css*
> + rm $(TARGET_DIR)/var/www/bootstrap/js/npm.js
> + rm $(TARGET_DIR)/var/www/bootstrap/js/bootstrap.js
> endef
>
> $(eval $(generic-package))
At this point, I am wondering if it is not simpler/shorter to install
only the necessary files, rather than install everything and remove
what's unneeded. Can you compare the two options?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-12 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 20:23 [Buildroot] [PATCH] bootstrap: remove development/debug files Yegor Yefremov
2015-01-12 21:00 ` Thomas Petazzoni [this message]
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=20150112220044.0db3d53b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox