Em Tue, 25 Jul 2006 18:30:53 +0100 (GMT Standard Time) John J Lee <[EMAIL PROTECTED]> escreveu:
> >> That's fine. However, a .deb-installed TG is more likely to break > >> and cause you debugging pain than is an easy_install-ed TG, IMHO. > >> That was my only point. > > > > Why? > [...] > > For the reasons that Philip Eby discussed in his post (to another > list) that I linked to in my original post here. Sure, but there are the answers by Mathias Klose, our Python maintainer in the follow up, and mine here in this thread, which, together, would answer most, if not all, of those points. The most obvious complaint that I see is that Debian packages are supposedly not using setuptools and not taking into account some very abstract concepts on how the Python software should be distributed. I'd invite people to look at the actual Debian packages for stuff like paste* and turbogears and decide if those arguments do apply. Those reasonings, though, would not make TG more likely to break or cause debugging pain, as you claimed (a claim still unsupported by anything). Just to be complete in my answer, one of the main points raised in the email you linked is this: ------------ Phillip responding to Mathias >So yes, if peak is a rather complex setup, it might be worthful to >have it as an example for a Debian package and to identify omissions >in Debian packaging practices and distutils/setuptools. This very statement helps to illustrate the impedance mismatch and communication difficulty. You appear to be interpreting my statement that e.g. SymbolTypes and ProxyTypes contain modules in the "peak" package (meaning #2) to imply that peak is or should be a Debian package (meaning #1, or perhaps a new meaning #3!). ---------------- Phillip clearly fails to understand a very simple thing about Debian packaging: while we can have a single source package for the whole peak "namespace", and various .deb files generated from it to provide each of SymbolTypes and ProxyTypes. That happens to paste, for example, which maps to this situation in some extent. So yeah, it does look like communication difficulty, to me. So, it seems to me that a lot of this "don't use it the Debian way" comes from assumptions caused maybe by lack of information on things actually work. Of course I welcome any Debian user to avoid using the packages and go ahead with using easy_install if they wish, or if they think this works better, but I believe some users will like to be able to use the way they're already used to when it comes to installing software to get TurboGears. See you, -- Gustavo Noronha Silva <[EMAIL PROTECTED]> http://people.debian.org/~kov/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
