[Cubicweb] Install of cubicweb-blog does not work properly
florent at secondweb.fr
Wed Sep 22 09:16:01 CEST 2010
Sylvain concerning the pyro dependency, I agree it should be discarded
in the base CW install : I have been writting CW applications for
several years at SecondWeb and just *never* used pyro, even on very
large systems like on http://www.118000.fr.
Dr Leo, if you intend to develop applications with CW, I think you
should consider using hg repos even without using the forest : using
simple scripts it is not that difficult to manage all the repos (I did
for a while, being stuck with a pretty old linux box).
2010/9/22 Sylvain Thénault <sylvain.thenault at logilab.fr>
> On 22 septembre 00:09, Dr.Leo wrote:
> > Hi,
> > Thanks for this mixed feedback. I understand that my detailed posts
> > about installation on Windows may bore those who have a working CW
> > environment. And frankly I would rather like to have one sooner than
> > later to get to the really interesting stuff. However, it appears
> > that installation on Linux is much better supported due to the more
> > mature packaging system than Windows. I also get the impression that
> > CW developers are keen to make it smoothly installable on Windows
> > which is - like it or not - a popular platform. And if I have to go
> > through a somewhat bumpy installation process I make an effort to
> > let people know what might be wrong rather than working silently for
> > myself which would arguably not contribute to solving any problem.
> and we're indeed thankful for that.
> > My concern regarding where cubes are installed is that there should
> > be a consistent policy. Either install them all in site-packages or
> > in Pythonxy/share/cubicweb/cubes/, but not some here and others
> > there depending on whether you use pip or not. So it is not about
> > some fiddling until it happens to work on my machine, but to make CW
> > installation more fun in the future. Before using symlinks or
> > whatever on Widnows I'd rather copy the package dir or egg file
> > somewhere else.
> Having a cube installed in site-packages rather the share/cubicweb/cubes
> when using pip/easy_install is definitly a bug in the cube installer
> (or in distribute/setuptools, but we should also find the workaround then).
> Does it work better with the trick I gave you ?
> > Back to the blog cube: I am not so sure if the Pyro dependency is
> > necessary given that the docs say that one can live without unless
> > one wants to use multiple machines.
> The pyro dependency is installed because the cube depends on cubicweb,
> which depends on pyro. And pyro is actually optional, but we've no
> way to express this with distribute/setuptools, so every recommended
> package is marked as a dependency. May be we should only add what's
> stricly necessary and let the user add alone optional packages.
> Sylvain Thénault LOGILAB, Paris (France)
> Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
> Développement logiciel sur mesure: http://www.logilab.fr/services
> CubicWeb, the semantic web framework: http://www.cubicweb.org
> Cubicweb mailing list
> Cubicweb at lists.cubicweb.org
Ce message est la propriété de SecondWeb et peut contenir des
informations confidentielles. Si vous n'êtes pas le destinataire
désigné, nous vous remercions de bien vouloir nous en aviser
immédiatement et de nous retourner ce message ou de le détruire, sans
faire un quelconque usage de son contenu, ni le communiquer ou le
diffuser, ni en prendre copie, électronique ou non.
This message is the property of SecondWeb and may contain confidential
information. If you are not the designated recipient, please notify us
immediately and return the message to us or destroy it, without making
any use whatsoever of the contents thereof. Furthermore you should not
forward or copy the message by electronic or other means.
More information about the Cubicweb