Here is a status on this ITP of TurboGears. As previously posted, the debianization of this package has become a political and technical adventure.
An executive summary of the .egg/.deb problem can be found here:
http://mail.python.org/pipermail/distutils-sig/2006-January/005873.html
The huge thread (details) of .egg/.deb issues can be found here:
http://mail.python.org/pipermail/distutils-sig/2005-November/005399.html
Technical problems that need to be resolved to debianize TurboGears are listed
below:
- TurboGears (TG) requires python egg support. Ian (upstream dev) has stated
that moving forward TG will be even "more broken" without .egg support.
http://mail.python.org/pipermail/distutils-sig/2005-November/005419.html
- Current debian policy and packaging tools disallow(?), disapprove(?) of the
current python .egg deployment method/locations.
http://mail.python.org/pipermail/distutils-sig/2005-November/thread.html
Some progress has been made to help address the .egg/.deb problems.
- Prelim support for .egg-info has been added to setuptool
http://mail.python.org/pipermail/distutils-sig/2005-December/005609.html
- Discussion, design, and coding is taking place to address, amongst other
things, the .egg/.deb issue:
http://lists.debian.org/debian-python/2006/01/msg00028.html
Here is what I think is needed to move forward:
- Debian Python policy (DPP) be updated to clearly state how python .eggs will
be supported
- Debian toolset/toolchain to build and deploy python .eggs in compliance with
the updated DPP.
Additionally, I think the following would be very helpful:
- Debian toolset to help migrate (rebuild?) python packages into DPP compliant
packages
- A way to identify packages that aren't DPP compliant
Progress is being made, but it is slow going. With out clear technical
direction regarding .egg/.deb support, I'm afraid TG will be a difficult code
base to package.
I very open to getting people onto the TG Alioth project:
https://alioth.debian.org/projects/pkg-turbogears/
Additional comments are welcome, especially if I have misrepresented any
technical information and it's effect on packaging TG.
I have also setup the pkg-turbogears-devel mailing list, as a place to discuss
the technical issues regarding packaging TG (alioth is telling me 6 to 24
hours for it to go live)
http://lists.alioth.debian.org/pipermail/pkg-turbogears-devel/
Thanks.
--
Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700
http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500
Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288
pgpOzNUccb8jn.pgp
Description: PGP signature
