> * trac should be able to work with an simple svn checkout.

While I'm not averse to this ability, I don't think that it's a show
stopper, or even one that really matters.
Having a checkout/compile cycle is standard practice.  Even then, once
it's setuptoolized, one will be able to simply say:

easy_install http://domain.com/path/to/repos

and have it install.

I would have liked to keep this feature as well: it is really nice not
to have an extra step (bypassing trac install) as it has been possible
up to now.

"installing" means that you have a copy of the actual files, which
implies that if you change the files in place - i.e. the installed
files - you cannot simply 'svn commit' them back to the repository

I'm not sure how many users do the same, but I have a customized
release of Trac (which cannot be easily implemented as plugins) that
is managed in a dedicated SVN repository. I would have liked being
able to develop and run Trac from the same location, since it's far
easier to manage than having a copy of the SVN files.

Maybe I missed something important here, and that this will still be
possible with the "python setup.py develop" thing. Please - let me
know.

Up to now, setuptools have really be a pain in the a... for me: issues
with their direct SVN internal data file parsing (move to svn 1.4),
deadlock at plugin load time caused by the site.py file, compatiblity
issues, problemS with proxy for installation over the network and many
other troubles that made me lose hours of work.

I do feel that setuptools is the way to go though: its ability to
manage dependencies is a great feature, especially for Trac and its
large and growing plugin base.

So I'm +1 for the merge, however I would have liked not to add another
trouble with the install/copy step.

Cheers,
Manu

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" 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/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to