On Mon, Sep 21, 2009 at 1:40 AM, Felix Schwarz
<[email protected]> wrote:
>
>
> Am 19.09.2009 17:12, schrieb Allen Bierbaum:
>>
>> Ok.  Thanks.  I didn't know easy_install was a required method for
>> installing Agilo.
>
> Actually the other method should work as well. However there are two
> potential problems:
> - So far we don't have automated tests for deploying Agilo inside an egg
> file (putting it in the plugins folder). Therefore it is much more likely
> that you encounter bugs.
> - trac won't warn you if some dependencies are not satisfied, it will just
> skip the module. easy_install tries to install the necessary dependencies
> itself.

Understood.  This is a bit of a pain for people like us that are
installing trac in a non-standard location and don't want to have trac
plugins / extensions show up in their system wide python packages.
For example, we have trac installed on one of our internal servers
that is used by multiple projects and we try to keep the trac
installation isolated from the rest of the system so we don't break
someone else's dependencies and they don't break ours.  In the future
if there were a way to install into the plugins directory, that would
be greatly appreciated.

Ok.  What is the "installation" method that is used for development?
For example if we wanted to modify the code and/or add a plugin, then
how would we install it into trac?  With the .eggs in the plugins
directory, we can put an egg link back to in development code to make
changes and test them on the fly.

-Allen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
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/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to