public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Python Probs
Date: Fri, 12 Jan 2001 11:07:39 +0100	[thread overview]
Message-ID: <3A5ED76B.B5A9B4FF@gottinger.de> (raw)
In-Reply-To: 20010112033108.A28324@kabbu.akopia.com

"Jerry A!" wrote:

> On Fri, Jan 12, 2001 at 08:57:17AM +0100, Achim Gottinger wrote:
> :
> : Do you think we need sys-devel/python-basic?  I think we can remove it
> : because we still have dev-lang/python.  In opposit to perl, python is
> : not required to build anythin in sys so we don't need python-basic any
> : longer.
>
> If I read Dan's previous e-mail correctly, it's dev-lang/python that
> should be going away.  Though, I do believe that now that we have
> sys-devel/python we can do away with sys-devel/python-basic.
>
>         --Jerry

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.
So dev-langy/python can not go away.
But in sys we only need spython with a basic set of libs. Libs must be
placed in /lib because spython is used
by env-update which is called during boot and so it must work without /usr
mounted.

-Achim-

>
>
> name:  Jerry Alexandratos         ||  Open-Source software isn't a
> phone: 703.599.6023               ||  matter of life or death...
> email: jerry@akopia.com           ||  ...It's much more important
>                                   ||  than that!
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev



  reply	other threads:[~2001-01-12 10:35 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 [this message]
2001-01-12 16:56             ` drobbins
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=3A5ED76B.B5A9B4FF@gottinger.de \
    --to=320095285153-0001@t-online.de \
    --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