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] python-pyxml: remove obsolete package
Date: Fri, 18 Dec 2015 22:40:21 +0100	[thread overview]
Message-ID: <20151218214021.GG27578@free.fr> (raw)
In-Reply-To: <20151218222828.26ba769f@free-electrons.com>

Thomas, All,

On 2015-12-18 22:28 +0100, Thomas Petazzoni spake thusly:
> On Wed, 16 Dec 2015 08:44:28 +0100, yegorslists at googlemail.com wrote:
> > From: Yegor Yefremov <yegorslists@googlemail.com>
> > 
> > PyXML is bitrotten and obsolete. You'll find the functionality it
> > previously provided is now included in the Python standard library.
> > 
> > So no need to keep this package in Buildroot anymore.
> > 
> > Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> > ---
> >  package/Config.in                      |  1 -
> >  package/python-pyxml/Config.in         | 12 ------------
> >  package/python-pyxml/python-pyxml.hash |  2 --
> >  package/python-pyxml/python-pyxml.mk   | 17 -----------------
> >  4 files changed, 32 deletions(-)
> >  delete mode 100644 package/python-pyxml/Config.in
> >  delete mode 100644 package/python-pyxml/python-pyxml.hash
> >  delete mode 100644 package/python-pyxml/python-pyxml.mk
> 
> As Yann said, can you respin this patch after taking care of
> Config.in.legacy handling ?
> 
> Or maybe instead of removing the package we should mark it as
> deprecated ?

I usually agree that we first mark package as being deprecated before we
get rid of them.

However, python-pyxml is so old, its features have long been incoporated
into python stdlib. Probably not many people are using it, if any at
all.

So, I'd vote in favour of just removing it altogether right now.

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:[~2015-12-18 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16  7:44 [Buildroot] [PATCH] python-pyxml: remove obsolete package yegorslists at googlemail.com
2015-12-16  8:32 ` Yann E. MORIN
2015-12-18 21:28 ` Thomas Petazzoni
2015-12-18 21:40   ` Yann E. MORIN [this message]
2015-12-18 21:45     ` Thomas Petazzoni
2015-12-18 22:31       ` Yegor Yefremov

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=20151218214021.GG27578@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