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/2] liberation: add support for custom target directory
Date: Wed, 12 Jan 2011 12:08:31 +0100	[thread overview]
Message-ID: <20110112120831.244cacff@surf> (raw)
In-Reply-To: <1294830195-11438-1-git-send-email-daniel.nystrom@timeterminal.se>

Hello,

On Wed, 12 Jan 2011 12:03:14 +0100
Daniel Nystr?m <daniel.nystrom@timeterminal.se> wrote:

> +if BR2_PACKAGE_LIBERATION
> +
> +config BR2_PACKAGE_LIBERATION_INSTALL_DIR
> +	string "Install directory"
> +	default "/usr/share/fonts/liberation"
> +	help
> +	  Target directory where the fonts should be installed
> +
> +endif

Why would this be necessary ?

In other words, which use case is this solving ? If it's a general font
location problem, maybe this should not be a Liberation-specific option.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-01-12 11:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 11:03 [Buildroot] [PATCH 1/2] liberation: add support for custom target directory Daniel Nyström
2011-01-12 11:03 ` [Buildroot] [PATCH 2/2] liberation: fixed misspelled target uninstall macro name Daniel Nyström
2011-01-12 11:08 ` Thomas Petazzoni [this message]
2011-01-12 13:14   ` [Buildroot] [PATCH 1/2] liberation: add support for custom target directory Daniel Nyström
  -- strict thread matches above, loose matches on Subject: below --
2011-01-12 13:51 Luca Ceresoli
2011-01-14  8:47 ` Thomas Petazzoni
2011-01-14 16:48   ` Luca Ceresoli
2011-01-14 17:12     ` Thomas Petazzoni
2011-01-15 12:23       ` Luca Ceresoli

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=20110112120831.244cacff@surf \
    --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