From: drobbins@gentoo.org
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Python Probs
Date: Fri, 12 Jan 2001 09:56:52 -0700 [thread overview]
Message-ID: <20010112095652.F20711@cvs.gentoo.org> (raw)
In-Reply-To: <3A5ED76B.B5A9B4FF@gottinger.de>; from 320095285153-0001@t-online.de on Fri, Jan 12, 2001 at 11:07:39AM +0100
On Fri, Jan 12, 2001 at 11:07:39AM +0100, Achim Gottinger wrote:
> Hmm, I always thought sys should contain everything that's required for
> building itself and everything that's required for a minimum runtime system.
> dev-lang/python includes tcl-tk support, sys-devel/python not otherwise we
> must must xfree/tcl-tk to sys which is a bad idea.
Hrm, I forgot about this problem since I compiled sys-devel/python on a system
without tcl-tk or X.
> ldd /usr/bin/python
libreadline.so.4.1 => /usr/lib/libreadline.so.4.1 (0x4001b000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40041000)
libncurses.so.5 => /lib/libncurses.so.5 (0x4006e000)
libdb-3.1.so => /usr/lib/libdb-3.1.so (0x400b2000)
libz.so.1 => /usr/lib/libz.so.1 (0x4012a000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40138000)
libdl.so.2 => /lib/libdl.so.2 (0x4014d000)
libutil.so.1 => /lib/libutil.so.1 (0x40150000)
libm.so.6 => /lib/libm.so.6 (0x40153000)
libc.so.6 => /lib/libc.so.6 (0x40171000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
I know this may sound weird at first, but I'd rather disable X11 and tcl/tk
support in sys-devel/python, and create a *third* python optional package --
python-x11. I don't want to force people to install Xfree86 and tcl/tk just
so they can get a reasonably complete python implementation. This kind of
thing would be a pain for people who are setting up a server without X at all,
but need a complete python to run their scripts.
Or, we can simply tell people that if you want X and tcl-tk support in your
python, just remerge sys-devel/python after you have X and tcl-tk installed.
the python configure program will detect that they're there, and link against
the new libraries. Of course, then we need a transparent method for you so
that when you're building packages, your sys-devel/python isn't linked against
X and tcl-tk stuff and will work on a base system.
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-01-12 16:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010111221517.A6248@kabbu.akopia.com>
[not found] ` <20010111203238.A12571@cvs.gentoo.org>
[not found] ` <20010111223449.A11743@kabbu.akopia.com>
2001-01-12 3:39 ` [gentoo-dev] Re: Python Probs drobbins
2001-01-12 7:57 ` Achim Gottinger
2001-01-12 8:31 ` Jerry A!
2001-01-12 10:07 ` Achim Gottinger
2001-01-12 16:56 ` drobbins [this message]
2001-01-12 16:35 ` Achim Gottinger
2001-01-12 17:12 ` drobbins
2001-01-12 17:02 ` Achim Gottinger
2001-01-12 17:50 ` drobbins
2001-01-12 17:46 ` Achim Gottinger
2001-01-12 20:12 ` [gentoo-dev] (s)python resolution drobbins
2001-01-12 17:59 ` [gentoo-dev] Re: Python Probs Jerry A!
2001-01-12 18:03 ` Thomas Flavel
2001-01-12 18:27 ` drobbins
2001-01-12 18:34 ` Thomas Flavel
2001-01-12 17:16 ` Jerry A!
2001-01-12 17:06 ` Achim Gottinger
2001-01-12 16:45 ` drobbins
2001-01-12 16:33 ` drobbins
2001-01-12 16:15 ` Achim Gottinger
2001-01-12 17:07 ` drobbins
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=20010112095652.F20711@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/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