On 7/1/07, Rustom Mody <[EMAIL PROTECTED]> wrote: > Yeah sure thats what is (finally) working but its never clear upfront > for a package what its dependency needs are -- linux version of DLL > hell. And it gets worse for systems that are little worlds in > themselves like python, ruby, eclipse, webmin etc. because they have > their own package-management systems which invariably quarell with the > native apt/rpm or whatever... > IMO the problem is two folds
1- distros and "little worlds" as you call them, not getting in sync as to why or how is the best way to handle packages. which results in incompatible installations, for example anything that installs with setuptools is almost 100% incompatible with anything installed by emerge,apt,etc. because in general (at least that's the case with distros I have used) they handle setuptools packages like normal distutils and handle the dependecies "externally". 2- setuptools/distutils having no uninstall option this is mainly because of the fact that noone has sit down and write a clear way to make sure a package is not needed anymore. which will clearly put setuptools in the land of apt or rpm, but then what happens when a setuptools package depends on something like gnome which isn't handle this way. so yes it's a big mess. > On 7/1/07, Thomas Jollans <[EMAIL PROTECTED]> wrote: > > On Sunday 01 July 2007, Rustom Mody wrote: > > > > > I first installed the debian package python-pysqlite1.1 using > > > synaptic. Since this seemed too old for other packages (sqlalchemy) I > > > downloaded the sources pysqlite-2.3.4.tar.gz and ran setup install. > > > > I wonder why you chose not to use python-pysqlite2... > > -- > > http://mail.python.org/mailman/listinfo/python-list > > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
