[oe-users] Overwhelmed by Python options

[Cliff Brake]

On 9/19/07, Yang <c17mswr02 at sneakemail.com> wrote:
> Hi, I'd like to include a trimmed-down Python 2.5 as part of my
> distro. I suppose I can try to do this manually, but there seems to
> already be a bunch of Python packages available. I'm trying to figure
> out what I should add to my top-level image .bb file.

DEPENDS = python

somewhere in your build should do it.  That will then create a host of
ipk packages that you can install.

> If these packages break up Python into smaller pieces, I'd like to be
> able to tell which pieces consist of what, so that I can pick and
> choose.

Build Python and then look in the tmp/deploy/.. dir:

compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/libpython2.5-1.0_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-audio_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-bsddb_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-codecs_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-compile_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-compiler_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-compression_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-core-dbg_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-core_2.5.1-ml3_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-crypt_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-curses_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-datetime_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-db_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-debugger_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-devel_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-distutils_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-email_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-fcntl_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-gdbm_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-hotshot_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-html_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-idle_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-image_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-io_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-lang_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-logging_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-mailbox_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-man_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-math_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-mime_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-misc_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-mmap_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-netclient_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-netserver_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-pickle_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-pprint_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-profile_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-pydoc_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-re_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-readline_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-resource_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-robotparser_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-shell_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-smtpd_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-sqlite3_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-stringold_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-subprocess_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-syslog_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-terminal_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-tests_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-textutils_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-threading_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-tkinter_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-unittest_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-unixadmin_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-xml_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-xmlrpc_2.5.1-ml1_armv5te.ipk
compulab-pxa270/tmp/deploy/glibc/ipk/armv5te/python-zlib_2.5.1-ml1_armv5te.ipk

Just add the needed pieces to your image bb.  Very granular packaging
is already done for you.

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com