15 Jul 23:11
Re: ets checkout of a specific revision
From: Dave Peterson <dpeterson@...>
Subject: Re: ets checkout of a specific revision
Newsgroups: gmane.comp.python.enthought.devel
Date: 2008-07-15 21:11:24 GMT
Subject: Re: ets checkout of a specific revision
Newsgroups: gmane.comp.python.enthought.devel
Date: 2008-07-15 21:11:24 GMT
Danny Shevitz wrote:
> Is there a way to use ets checkout to checkout a specific version number?
>
I think this one was addressed in other e-mails (it is not yet possible)
but you can individually manipulate each project by doing an 'svn up -r
<rev number>' yourself. For example, if you want to see if this
problem existed in Traits as of revision 19500, do:
cd ETS_3.0.0b1/Traits_3.0.0b1
svn up -r 19500
python setup.py develop
> I think I have discovered a newly introduced bug (see my separate thread),
> and I would like to see if I can figure out which version it was introduced in.
>
> Also, if this is possible, how would I use ets develop to develop the older
> revision.
> Ets develop seems think I have the more recent version so I doesn't clear out
> the old version. How do I "remove" a newer version in favor of an old one?
>
The "ets develop" command simply iterates through all the project source
directories in your checkout and does an"python setup.py develop" on
each. This command will build the source in-place and make it the
current version in your python environment by effectively treating your
in-place source as the contents of an egg. As a result, if you svn up
to any version for any (or all) child projects in the checkout, doing an
"ets develop" on the checkout will simply make those versions active
whether they are older revisions or newer ones. I hope this is clear.
I'm having some difficulty figuring out a better way to explain it.
-- Dave
RSS Feed