From: Nick Jones <carpaski@twobit.net>
To: Alastair Tse <liquidx@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] python-2.3.2 testing required
Date: Thu, 13 Nov 2003 02:07:33 -0600 [thread overview]
Message-ID: <20031113080733.GA32077@twobit.net> (raw)
In-Reply-To: <1068662803.18867.134.camel@huggins.eng.cam.ac.uk>
> * Even though python-2.3.2 requires portage-2.0.49-r16, I can't put a
> dep in otherwise it may create a circular dependency. Probably the best
> solution would be to have a pkg_setup check before it goes ahead.
That might be acceptable. python and portage will always be present
on a Gentoo system. It's a litle weird, but may benefit everyone in
this situation. I'll get around to testing this soon. I'd prefer
that portage be ~arch before you make python ~arch, as it'll cause
headaches otherwise. The only reason I haven't yet is that it can
break the GUI's for portage. I'll be notifing the authors to be
sure that they are up to date, as soon as I have internet access
again. It's down as I'm writing this email.
> * Maybe we should think about using a non version specific directory for
> Python modules to ease upgrade.
I agree.
--NJ
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-11-13 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 18:46 [gentoo-dev] python-2.3.2 testing required Alastair Tse
2003-11-13 8:07 ` Nick Jones [this message]
2003-11-13 9:57 ` Alastair Tse
2003-11-13 8:07 ` Alastair Tse
2003-11-13 9:05 ` Paul de Vrieze
2003-11-13 9:38 ` Alastair Tse
2003-11-13 9:10 ` Toby Dickenson
2003-11-13 9:51 ` Alastair Tse
2003-11-13 23:34 ` Toby Dickenson
2003-11-14 9:37 ` Alastair Tse
2003-11-15 8:09 ` Simon Watson
2003-11-17 0:29 ` Alastair Tse
2003-11-17 10:28 ` Toby Dickenson
2003-11-17 10:48 ` Alastair Tse
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=20031113080733.GA32077@twobit.net \
--to=carpaski@twobit.net \
--cc=gentoo-dev@gentoo.org \
--cc=liquidx@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