Sorry this 2 posts but I have now a clean installation of tg2 from
subversion. I have changed th tg2/setup.py like you can see bellow
with all my commands to install tg2:


$ virtualenv --no-site-packages tg2env
New python executable in tg2env/bin/python
Installing setuptools............done.
$ source tg2env/bin/activate

(tg2env)$ cd ../tmpsvn
(tg2env)$ hg clone http://pylonshq.com/hg/pylons-dev Pylons
(tg2env)$ cd Pylons
(tg2env)$ python setup.py develop
(tg2env)$ cd ..

# tg2 dependency ?
(tg2env)$ easy_install -Z zope.interface
(tg2env)$ easy_install -Z PasteScript==dev
(tg2env)$ easy_install -Z genshi
(tg2env)$ easy_install -Z toscawidgets

(tg2env)$ svn co http://svn.turbogears.org/trunk tg2
(tg2env)$ svn co http://svn.turbogears.org/projects/tg.devtools/trunk
tgdev
(tg2env)$ svn co http://svn.repoze.org/repoze.what/trunk/ repoze.what
(tg2env)$ svn co http://svn.repoze.org/repoze.what/plugins/sql/trunk
repoze.what.plugins.sql

(tg2env)$ cd repoze.what
(tg2env)$ python setup.py develop
(tg2env)$ cd ../repoze.what.plugins.sql
(tg2env)$ python setup.py develop
(tg2env)$ cd ..

(tg2env)$ svn diff tg2/
Index: tg2/setup.cfg
===================================================================
--- tg2/setup.cfg       (revisão 5707)
+++ tg2/setup.cfg       (cópia de trabalho)
@@ -61,5 +61,5 @@
 # dotpath: /usr/local/bin/dot

 [easy_install]
-index_url = http://turbogears.org/2.0/downloads/current/
+index_url = http://turbogears.org/2.0/downloads/current/index


(tg2env)$ cd tg2
(tg2env)$ python setup.py develop
(tg2env)$ cd ../tgdev
(tg2env)$ python setup.py develop



On 18 Nov, 10:46, Helio Pereira <[EMAIL PROTECTED]> wrote:
> Another thing :-P
>
> I have Pylons installed from mercury and tg2 dependency don't like it:
>
> $ python -c "import pylons; print pylons.__version__"
> 0.9.7dev-20081118
>
> """
> Processing dependencies for TurboGears2==1.9.7b1dev-r5691
> Searching for Pylons>=0.9.7beta3
> Readinghttp://turbogears.org/2.0/downloads/current/Pylons/
> Couldn't retrieve index page for 'Pylons'
> Scanning index of all packages (this may take a while)
> Readinghttp://turbogears.org/2.0/downloads/current/
> No local packages or download links found for Pylons>=0.9.7beta3
> error: Could not find suitable distribution for Requirement.parse
> ('Pylons>=0.9.7beta3')
> """
>
> On 18 Nov, 10:39, Helio Pereira <[EMAIL PROTECTED]> wrote:
>
> > I'm having problems with sqlalchemy dependency like you can see
> > bellow. I think its the name "0.5.0beta3" in the site and not
> > "0.5beta3" in the dependency  "SQLAlchemy>=0.5beta3"
>
> > """
> > Processing dependencies for TurboGears2==1.9.7b1dev-r5691
> > Searching for SQLAlchemy>=0.5beta3
> > Readinghttp://turbogears.org/2.0/downloads/current/SQLAlchemy/
> > Couldn't find index page for 'SQLAlchemy' (maybe misspelled?)
> > Scanning index of all packages (this may take a while)
> > Readinghttp://turbogears.org/2.0/downloads/current/
> > No local packages or download links found for SQLAlchemy>=0.5beta3
> > error: Could not find suitable distribution for Requirement.parse
> > ('SQLAlchemy>=0.5beta3')
> > """
>
> > On 17 Nov, 16:52, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
>
> > > > On Monday November 17, 2008 17:19:24 Mark Ramm wrote:
> > > >> We still have to add that to the online repository, I'll take care of
> > > >> that right away.
>
> > > > It's already in the repository, I think we just need to update this:
> > > >http://www.turbogears.org/2.0/downloads/current/index/
>
> > > Yea, that's what I fund.   Website index is updated now.
>
> > > I need to make a /trunk/index for SVN install or something, current is
> > > still designed to be for the existing "stable" release.
>
> > > --Mark Ramm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to