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] Package conversion for 2010.08
Date: Sun, 30 May 2010 12:36:55 +0200	[thread overview]
Message-ID: <20100530123655.6cffcc8c@surf> (raw)

Hello,

Release 2010.05 will soon be released by Peter and therefore I'd like
to make a new status of the package conversion effort. For the record,
the previous status of this effort was given on March, 14th:

 http://lists.busybox.net/pipermail/buildroot/2010-March/032840.html

At that time, we had 61 packages to convert to the generic package
infrastructure, and 107 to convert to the autotools infrastructure.

As of today's Git version, we are now at 56 packages to convert to the
generic package infrastructure and 77 packages to convert to the
autotools infrastructure.

Your help would be very appreciated in speeding up this conversion
effort. Before doing any conversion, check our Bugzilla to see if
someone else has already done the conversion work for your package.

Packages to convert to the autotools infrastructure
===================================================

 * alsa-utils
 * axel
 * bash
 * berkeleydb
 * boa
 * coreutils
 * cups
 * cvs
 * dash
 * dhcp
 * dhcpdump
 * dialog
 * diffutils
 * dillo
 * distcc
 * dmalloc
 * fbv
 * file
 * gawk
 * gettext
 * gmp
 * gtk2-engines
 * gzip
 * hal
 * icu
 * imagemagick
 * iproute2
 * ipsec-tools
 * libeXosip2
 * libfuse
 * libglib12
 * libgpg-error
 * libgtk12
 * liblockfile
 * links
 * lrzsz
 * ltrace
 * lvm2
 * madplay
 * make
 * module-init-tools
 * modutils
 * mpfr
 * mpg123
 * mplayer
 * netkitbase
 * netkittelnet
 * netsnmp
 * newt
 * nfs-utils
 * ntp
 * pciutils
 * pptp-linux
 * prboom
 * proftpd
 * python
 * qt
 * quagga
 * rp-pppoe
 * ruby
 * rxvt
 * sdl
 * sdl_mixer
 * sdl_ttf
 * sed
 * socat
 * stunnel
 * sudo
 * tftpd
 * thttpd
 * tn5250
 * util-linux
 * valgrind
 * vim
 * xerces
 * xfsprogs
 * zlib

Packages to convert to the generic infrastructure
=================================================

 * acpid
 * bsdiff
 * busybox
 * concierge
 * devmem2
 * doom-wads
 * dosfstools
 * ezxml
 * fbset
 * fconfig
 * festival
 * festlex
 * festvox
 * fis
 * gadgetfs-test
 * hdparm
 * hotplug
 * hwdata
 * input-tools
 * iostat
 * l2tp
 * liberation
 * libfloat
 * lmbench
 * lm-sensors
 * lockfile-progs
 * logrotate
 * lsof
 * ltp-testsuite
 * makedevs
 * matchbox
 * mcookie
 * memtester
 * microcom
 * microperl
 * microwin
 * mii-diag
 * mrouted
 * netplug
 * pcmcia
 * portage
 * portmap
 * procps
 * sfdisk
 * slang
 * sysklogd
 * sysvinit
 * tinyhttpd
 * ttcp
 * uemacs
 * usbmount
 * vpnc
 * vsftpd
 * webif
 * wipe
 * wireless-tools

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

             reply	other threads:[~2010-05-30 10:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30 10:36 Thomas Petazzoni [this message]
2010-06-07  9:17 ` [Buildroot] Package conversion for 2010.08 Thomas Petazzoni
2010-06-07  9:37   ` Kelvin Cheung
2010-06-07 10:28     ` Thomas Petazzoni
2010-06-08  7:47       ` Kelvin Cheung
2010-06-07 13:46   ` Peter Korsgaard

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=20100530123655.6cffcc8c@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