Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4 of 5 v2] lzma: remove deprecated target package
Date: Mon, 20 Jan 2014 22:58:52 +0100	[thread overview]
Message-ID: <20140120215852.GG3421@free.fr> (raw)
In-Reply-To: <ad3654061390422916af.1390254369@argentina>

Thomas, All,

On 2014-01-20 22:46 +0100, Thomas De Schampheleire spake thusly:
> The on-target lzma package has been deprecated for a long time, so remove
> it. This does not remove the support for generating lzma-compressed rootfs
> images.
> 
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
[--SNIP--]
> diff --git a/Config.in.legacy b/Config.in.legacy
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -99,6 +99,16 @@ comment "-------------------------------
>  endif
>  
>  ###############################################################################
> +comment "Legacy options removed in 2014.02"
> +
> +config BR2_PACKAGE_LZMA
> +	bool "lzma target package has been removed"
> +	select BR2_LEGACY
> +	help
> +	  The 'lzma' target package has been removed since it has been
> +	  deprecated for more than four buildroot releases.
> +	  Note: generating lzma-compressed rootfs images is still supported.
> +
>  config BR2_PACKAGE_LIBNFC_LLCP
>  	bool "libnfc-llcp has been removed"
>  	depends on BR2_TOOLCHAIN_HAS_THREADS # libusb
> @@ -109,9 +119,6 @@ config BR2_PACKAGE_LIBNFC_LLCP
>            to 'libllcp'. We have added a new package for 'libllcp' and bumped
>            the version at the same time.
>  
> -###############################################################################
> -comment "Legacy options removed in 2014.02"
> -

Moving the comment will gonna clash with my recent patch being applied
by Peter:
    http://git.buildroot.org/buildroot/commit/?id=f169e5e1055600fda1b3ff0c852ee84d2ec80460

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-01-20 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 21:46 [Buildroot] [PATCH 0 of 5 v2] Deprecation: clarify manual, remove ttcp and lzma Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 1 of 5 v2] manual: clarify handling of deprecated features Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 2 of 5 v2] ttcp: remove deprecated package Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 3 of 5 v2] flex: change config text of 'target binary' option Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 4 of 5 v2] lzma: remove deprecated target package Thomas De Schampheleire
2014-01-20 21:58   ` Yann E. MORIN [this message]
2014-01-21  7:56     ` Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 5 of 5 v2] Config.in.legacy: fix misc. problems with libnfc-llcp removal Thomas De Schampheleire

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=20140120215852.GG3421@free.fr \
    --to=yann.morin.1998@free.fr \
    --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