All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/freetype
Date: Fri, 5 Sep 2008 22:53:03 +1000	[thread overview]
Message-ID: <20080905125303.GA31755@cloud.net.au> (raw)
In-Reply-To: <87iqtagbry.fsf@macbook.be.48ers.dk>

On Fri, Sep 05, 2008 at 11:52:33AM +0200, Peter Korsgaard wrote:
>  hamish> Changeset:
>  hamish> Modified: trunk/buildroot/package/freetype/Config.in
>  hamish> ===================================================================
>  hamish> --- trunk/buildroot/package/freetype/Config.in	2008-09-04 16:16:47 UTC (rev 23324)
>  hamish> +++ trunk/buildroot/package/freetype/Config.in	2008-09-05 01:03:45 UTC (rev 23325)
>  hamish> @@ -16,12 +16,12 @@
>  hamish>  	config BR2_FREETYPE_VERSION_2_2_1
>  hamish>  		bool "Freetype 2.2.1"
>  
>  hamish> -	config BR2_FREETYPE_VERSION_2_3_5
>  hamish> -		bool "Freetype 2.3.5"
>  hamish> +	config BR2_FREETYPE_VERSION_2_3_7
>  hamish> +		bool "Freetype 2.3.7"
> 
> Please use 2_3_x like we do it for busybox and haserl so kconfig will
> do the right thing when you update your buildroot snapshot.

Hi Peter,

That sounds good but I'm not really sure what you mean?


choice
	prompt "BusyBox Version"
	depends on BR2_PACKAGE_BUSYBOX
	default BR2_BUSYBOX_VERSION_1_12_X
	help
	  Select the version of BusyBox you wish to use.

	config BR2_BUSYBOX_VERSION_1_2_2_1
		bool "BusyBox 1.2.2.1"
		depends on BR2_DEPRECATED

	[...]
endchoice

config BR2_BUSYBOX_VERSION
	string
	default "1.2.2.1"	if BR2_BUSYBOX_VERSION_1_2_2_1
	default "1.6.1"		if BR2_BUSYBOX_VERSION_1_6_1
	default "1.7.5"		if BR2_BUSYBOX_VERSION_1_7_X
	default "1.8.3"		if BR2_BUSYBOX_VERSION_1_8_X
	default "1.9.2"		if BR2_BUSYBOX_VERSION_1_9_X
	default "1.10.4"	if BR2_BUSYBOX_VERSION_1_10_X
	default "1.11.2"	if BR2_BUSYBOX_VERSION_1_11_X
	default "1.12.0"	if BR2_BUSYBOX_VERSION_1_12_X


How's it different?

Thanks and regards
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-09-05 12:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  1:03 [Buildroot] svn commit: trunk/buildroot/package/freetype hamish at uclibc.org
2008-09-05  9:52 ` Peter Korsgaard
2008-09-05 12:53   ` Hamish Moffatt [this message]
2008-09-05 18:31     ` Peter Korsgaard
2008-09-06  4:22       ` Hamish Moffatt
2008-09-05 17:44   ` danieljlaird at hotmail.com
  -- strict thread matches above, loose matches on Subject: below --
2009-01-24 10:20 jacmet at uclibc.org
2009-01-24  8:31 jacmet at uclibc.org
2009-01-16  9:02 laird at uclibc.org
2009-01-08  8:27 jacmet at uclibc.org
2008-12-08 13:42 jacmet at uclibc.org
2008-12-08  4:43 hamish at uclibc.org
2008-11-11 11:33 laird at uclibc.org
2009-01-24  8:28 ` Peter Korsgaard
2008-11-10 21:43 hartleys
2008-10-09 12:50 laird at uclibc.org
2008-07-17 13:20 jacmet at uclibc.org
2008-07-04  2:57 correa at uclibc.org
2008-07-05 19:08 ` Peter Korsgaard
2008-05-22 21:30 ulf at uclibc.org
2008-04-25 16:45 ninevoltz at uclibc.org
2008-03-06 18:10 ninevoltz at uclibc.org
2007-11-16 10:16 vanokuten at uclibc.org
2007-09-23  9:55 ulf at uclibc.org
2007-08-14  6:28 ulf at uclibc.org
2007-01-16 19:51 aldot at uclibc.org
2007-01-10 23:54 andersen at uclibc.org

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=20080905125303.GA31755@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.