From 0ade7357a2df463243a41d3e4410e7ed3de8d17a Mon Sep 17 00:00:00 2001
From: Ned Batchelder <ned@nedbatchelder.com>
Date: Sun, 20 Sep 2009 18:05:07 -0400
Subject: New theory about how to kit for py3k: coverage3k-* kits are for 3.x

---
 allkits.cmd | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

(limited to 'allkits.cmd')

diff --git a/allkits.cmd b/allkits.cmd
index 1e4fe22..a83cac7 100644
--- a/allkits.cmd
+++ b/allkits.cmd
@@ -8,19 +8,18 @@ python setup.py bdist_wininst
 call \ned\bin\switchpy 26
 python setup.py bdist_wininst
 
-@REM Source kit: Py2k in "coverage", Py3k in "py3k"
-del /q py3k\*.*
-mkdir py3k
-xcopy /s/h/i/e /exclude:notsource.txt three\coverage\*.py py3k
 set TAR_OPTIONS=--group=100
 python setup.py sdist --formats=gztar
 set TAR_OPTIONS=
 
-@REM py3k windows kit: code still needs to be in py3k, so move it.
+@REM Py3k
 cd three
 call \ned\bin\switchpy 31
-xcopy /s/h/i/e coverage py3k
 python setup.py bdist_wininst
-rmdir/s/q py3k
+
+set TAR_OPTIONS=--group=100
+python setup.py sdist --formats=gztar
+set TAR_OPTIONS=
+
 cd ..
-copy three\dist\*.exe dist
+copy three\dist\*.* dist
-- 
cgit v1.2.1