Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] font-awesome:new package
Date: Tue, 16 Feb 2016 22:03:59 +0100	[thread overview]
Message-ID: <20160216220359.6b79146a@free-electrons.com> (raw)
In-Reply-To: <1455601427-20322-1-git-send-email-atul.singh.mandla@rockwellcollins.com>

Hello Atul,

Thanks for this contribution! Looks mostly good, I have a few comments
though, see below.

On Tue, 16 Feb 2016 11:13:47 +0530, Atul Singh wrote:
>  Font Awesome is a full suite of 605 pictographic icons for easy
>  scalable vector graphics on websites.

Initial space at the beginning of each line is not needed.

> diff --git a/package/Config.in b/package/Config.in
> index a5b31aa..a2bd46e 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -854,6 +854,7 @@ menu "Graphics"
>  	source "package/cairomm/Config.in"
>  	source "package/exiv2/Config.in"
>  	source "package/fltk/Config.in"
> +	source "package/font-awesome/Config.in"
>  	source "package/fontconfig/Config.in"
>  	source "package/freetype/Config.in"
>  	source "package/gd/Config.in"

This package should rather go in the "Fonts, cursors, icons, sounds and
themes" menu, sub-menu "Icons".

> diff --git a/package/font-awesome/font-awesome.mk b/package/font-awesome/font-awesome.mk
> new file mode 100644
> index 0000000..acaa3d8
> --- /dev/null
> +++ b/package/font-awesome/font-awesome.mk
> @@ -0,0 +1,23 @@
> +################################################################################
> +#
> +# font-awesome
> +#
> +################################################################################
> +
> +FONT_AWESOME_VERSION = v4.5.0
> +FONT_AWESOME_SITE = $(call github,FortAwesome,Font-Awesome,$(FONT_AWESOME_VERSION))
> +FONT_AWESOME_LICENSE = OFLv1.1, MIT

License would be more precise with:

	OFLv1.1 (font), MIT (CSS, LESS and Sass files)

> +FONT_AWESOME_LICENSE_FILES = css/font-awesome.css

This is not a license text, it only repeats that it's under OFLv1.1
(font) and MIT (CSS). So I'd say, just don't specify any LICENSE_FILES.

> +FONT_AWESOME_DIRECTORIES_LIST = css fonts less scss

Out of curiosity, can you explain in which situation are the "less" and
"scss" directories useful ?

> +define FONT_AWESOME_INSTALL_TARGET_CMDS
> +	# Install required directories

Comment is not very useful.

> +	for dir in $(FONT_AWESOME_DIRECTORIES_LIST); \
> +	do \
> +		$(INSTALL) -d $(TARGET_DIR)/usr/share/font-awesome/$$dir && \
> +		$(INSTALL) -m 0644 -t $(TARGET_DIR)/usr/share/font-awesome/$$dir \
> +			$(@D)/$$dir/*.* || exit 1; \

We generally use "cp -dpfr" to copy full directories. What about simply:

	mkdir -p $(TARGET_DIR)/usr/share/font-awesome/
	$(foreach d,$(FONT_AWESOME_DIRECTORIES_LIST),\
		cp -dpfr $(@D)/$(d) $(TARGET_DIR)/usr/share/font-awesome$(sep))

Could you take into account those comments, and send an updated version?

Thanks a lot!

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

  reply	other threads:[~2016-02-16 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  5:43 [Buildroot] [PATCH 1/1] font-awesome:new package Atul Singh
2016-02-16 21:03 ` Thomas Petazzoni [this message]
2016-02-17  7:12   ` Atul Singh Mandla
2016-02-17  7:50     ` Thomas Petazzoni

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=20160216220359.6b79146a@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