From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pkg-perl infra V5 8/8] cpanminus: remove it
Date: Mon, 10 Feb 2014 19:29:16 +0100 [thread overview]
Message-ID: <20140210192916.669fb580@skate> (raw)
In-Reply-To: <CAB0FRsvVCz71SAY=_5jev+eDjChszCVX00eQ4oa_DEYH2YcbCA@mail.gmail.com>
Dear Fran?ois Perrad,
On Sat, 8 Feb 2014 09:18:08 +0100, Fran?ois Perrad wrote:
> 2014-02-07 21:50 GMT+01:00 Thomas De Schampheleire <patrickdepinguin@gmail.com>:
> > Hi Fran?ois,
> >
> > On Fri, Feb 7, 2014 at 9:55 AM, Francois Perrad <fperrad@gmail.com> wrote:
> >> cpanminus was marked as broken, now it becomes useless with the Perl infrastructure.
> >>
> >> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> >> ---
> >> package/Config.in | 1 -
> >> package/cpanminus/Config.in | 40 ----------------------------------
> >> package/cpanminus/cpanminus.mk | 47 ----------------------------------------
> >> 3 files changed, 88 deletions(-)
> >> delete mode 100644 package/cpanminus/Config.in
> >> delete mode 100644 package/cpanminus/cpanminus.mk
> >>
> >
> > Shouldn't we add an entry in Config.in.legacy for the removed symbol?
> >
>
> Perhaps, we could do an exception.
> The log of package/cpanminus/Config.in contains only 2 entries :
> * cpanminus: mark as broken Thomas Petazzoni 2012-11-16
> * cpanminus: new package Francois Perrad 2012-11-03
I agree with Fran?ois. cpanminus was marked as broken very quickly
after it was introduced, and broken packages cannot be selected in
menuconfig. cpanminus has never been selectable in any Buildroot
stable release, so there is no need to keep compatibility.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-10 18:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:55 [Buildroot] [pkg-perl infra V5 0/8] a package infrastructure for Perl/CPAN modules Francois Perrad
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 1/8] host-perl: refactor and rename PERL5LIB Francois Perrad
2014-02-10 7:07 ` Arnout Vandecappelle
2014-02-10 7:17 ` Arnout Vandecappelle
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 2/8] pkg-perl: new infrastructure Francois Perrad
2014-02-07 20:33 ` Thomas De Schampheleire
2014-02-10 7:16 ` Arnout Vandecappelle
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 3/8] scancpan: a new script Francois Perrad
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 4/8] host-perl-xml-parser: rename and refactor with perl infrastructure Francois Perrad
2014-02-07 20:36 ` Thomas De Schampheleire
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 5/8] host-perl-module-build: new package Francois Perrad
2014-02-07 20:41 ` Thomas De Schampheleire
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 6/8] perl: remove useless patch Francois Perrad
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 7/8] manual: adding packages perl Francois Perrad
2014-02-07 20:49 ` Thomas De Schampheleire
2014-02-08 9:00 ` François Perrad
2014-02-07 8:55 ` [Buildroot] [pkg-perl infra V5 8/8] cpanminus: remove it Francois Perrad
2014-02-07 20:50 ` Thomas De Schampheleire
2014-02-08 8:18 ` François Perrad
2014-02-10 18:29 ` Thomas Petazzoni [this message]
2014-02-10 18:56 ` 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=20140210192916.669fb580@skate \
--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