While I agree with you, that's really not the "Debian way" of doing it and a lot of people that run Debian want it to be that way for a reason. It's unfortunate that Debian can't keep on top of rapidly moving platforms like Plone but there's not a lot you can do except what you recommend: install from source.
Myself, I use apt to manage Zope and Python on my Debian/Ubuntu box and manually deal with Plone. At least this way I keep dealing with dependencies to a minimum and all I need to worry about is the dependencies of different Zope/Plone products and not my entire system. Shane On 3/3/06, Nick Davis <[EMAIL PROTECTED]> wrote: > > > > > It's probably a packaging issue with the Debian install, half of our > > install issues are from Debian people. Please contact the maintainer if > > it doesn't work as it should. > > > FYI We use Plone 2.1.2, Zope 2.8.5, Python 2.3.5 on Debian Sarge, and > avoid all such installation problems by avoiding Debian packages and > building our own python and zope. > > I would recommend other people on Debian to do the same. > > Nick > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > -- http://liquid.homelinux.org/ _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
