From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] vim: be more careful when removing the documentation
Date: Mon, 5 Dec 2016 23:04:58 +0100 [thread overview]
Message-ID: <20161205230458.3a8ea9d9@free-electrons.com> (raw)
In-Reply-To: <1480970192-13208-1-git-send-email-thomas.petazzoni@free-electrons.com>
Hello,
On Mon, 5 Dec 2016 21:36:32 +0100, Thomas Petazzoni wrote:
> The current VIM_REMOVE_DOCS hook removes all .txt files from
> /usr/share/vim. Unfortunately, this also removes the rgb.txt file,
> which is needed at runtime for vim, as reported in bug #9466.
>
> This commit changes VIM_REMOVE_DOCS to remove only
> /usr/share/vim/vim80/doc/. Size-wise, it's equivalent because:
>
> - We are no longer removing a few README.txt in other directories,
> taking more space.
>
> - We are now removing the /usr/share/vim/vim*/doc/ folder entirely,
> which contained a few files not named *.txt
>
> So overall, the size of /usr/share/vim/ before and after this patch is
> still 11MB.
>
> Fixes bug #9466.
>
> Reported-by: Mateusz Furdyna <sir.ferdek@gmail.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Changes since v1:
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-12-05 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 20:36 [Buildroot] [PATCHv2] vim: be more careful when removing the documentation Thomas Petazzoni
2016-12-05 21:46 ` Arnout Vandecappelle
2016-12-05 22:04 ` 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=20161205230458.3a8ea9d9@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