[arch-dev-public] Plan for python upgrade

Aaron Griffin aaronmgriffin at gmail.com
Mon Oct 6 20:02:42 EDT 2008

On Mon, Oct 6, 2008 at 12:49 AM, Jason Chu <jason at archlinux.org> wrote:
> I'm going with Aaron's suggestion.  Don't worry about python 3.0 until
> more things support it.  Or create a temporary python3 repo to support
> software in there (and call the package python3) for people who really
> want it.  Then the python/python2 split will be gentler.

Yeah, instead of using 'extrapkg', just use 'archrelease python3-i686'
or something, and manually scp the packages to gerolde (or maybe patch
devtools to do this for you). Then, on gerolde, you can do
"/arch/db-update i686 python3", though that'd require someone with
superpowers manually making a top-level dir.

I think this route would be best - just tell users how to get the
python3 repo, and bam. All the tools are made to do exactly this, and
considering the python3 upgrade path will take weeks, not days, it
makes perfect sense to use a side repo for this until we're at a level
of support where we want to move it into testing/extra.

More information about the arch-dev-public mailing list