Re: [PyWrapper-devel] Libraries distribution in PyWrapper

[<m.d...@BG...>]

So lets include a new directory called "installer" in the project.
If we dont like the name we can change it later, but I cant think of any =
better right now.
I will add some of the libs already. But remember to only use the source =
installers, never the comiled stuff.

-- Markus
 =20

> -----Urspr=FCngliche Nachricht-----
> Von: pyw...@li...=20
> [mailto:pyw...@li...] Im=20
> Auftrag von D=F6ring, Markus
> Gesendet: Mittwoch, 2. August 2006 14:31
> An: PyWrapper Developers mailing list; Javier privat
> Betreff: Re: [PyWrapper-devel] Libraries distribution in PyWrapper
>=20
> mx.DateTime alone is also open source.
> http://www.egenix.com/files/python/mxDateTime.html#Copyright
>=20
> their own kind of license, but I cant see any problem distributing it:
> http://www.egenix.com/files/python/mxLicense.html#Public
>=20
>=20
> -- Markus
>  =20
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: pyw...@li...
> > [mailto:pyw...@li...] Im=20
> Auftrag von=20
> > Javier privat
> > Gesendet: Mittwoch, 2. August 2006 12:24
> > An: PyWrapper Developers mailing list
> > Betreff: [PyWrapper-devel] Libraries distribution in PyWrapper
> >=20
> > Hi,
> >=20
> > I was wondering if we could change a bit our strategy for deploying=20
> > PyWrapper. Right now to install it you have to install:
> >=20
> > 1)PyXML
> > 2)mxDateTime
> > 3)CherryPy
> > 4)elementtree
> > 5)kid
> >=20
> > Then you probably will also need:
> >=20
> > 6) libxml2
> > 7) a database module
> >=20
> > and finally if you want BioMOBY support now I will also be=20
> requiring:
> >=20
> > 8) fpconst
> > 9) SOAPpy
> > 10) BioMOBY Python
> >=20
> > This is getting a little bit horrible to install. I think most of=20
> > these libraries, I think actually all, can be legally redistributed=20
> > with other software so I was wondering if we could not embed=20
> > everything into PyWrapper.
> >=20
> > Well, I know there are some problems. Some of these=20
> libraries need to=20
> > be compiled in unix and therefore installation is needed. But in=20
> > Windows we might be able to distribute them already=20
> compiled. In the=20
> > case of unix we can at least include them in the package=20
> and provide=20
> > an installer that install all of them into our external_lib=20
> directory.
> >=20
> > We can have something like /lib/external_lib folder where=20
> we include=20
> > all this stuff. Do you know what happens if we install a certain=20
> > version of a library there and the user has already the=20
> same library=20
> > installed on his python? Which one will take preference?
> >=20
> > And there is still the open issue of which library to use=20
> for xslt...
> > we are not happy with none of them and they are all difficult to=20
> > install in mac os x. Any ideas?
> >=20
> > Cheers.
> >=20
> > --------------------------------------------------------------
> > -----------
> > Take Surveys. Earn Cash. Influence the Future of IT Join=20
> > SourceForge.net's Techsay panel and you'll get the chance to share=20
> > your opinions on IT & business topics through brief surveys -- and=20
> > earn cash=20
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
> &CID=3DDEVDEV
> > _______________________________________________
> > PyWrapper-devel mailing list
> > PyW...@li...
> > https://lists.sourceforge.net/lists/listinfo/pywrapper-devel
> >=20
>=20
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT Join=20
> SourceForge.net's Techsay panel and you'll get the chance to=20
> share your opinions on IT & business topics through brief=20
> surveys -- and earn cash=20
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> PyWrapper-devel mailing list
> PyW...@li...
> https://lists.sourceforge.net/lists/listinfo/pywrapper-devel
>=20