John Hampton wrote:
Ilias Lazaridis wrote: > * vendors should be able to provide a "product" (collection of plugins > and related configuration)
[...] (comments)
> * trac should be able to work with an simple svn checkout.
[...] (comments)
> * Environment Inheritance should be multi-level, with the ability to > change the base environment manually.
[...] (comments) (I apologize for not answering in detail) The requirements result out of a real-life use-case. The resulting requirements are of general nature - their implementation would increase the flexibility of the trac framework. Python is a dynamic language - thus it should work like that: dynamic, if needed. Setuptools can become an "innovation cancer", if it is used without care. The Requirement: Allow svn checkout of different trac development constellations (trac version, several plugins and a specific config file). Practical use-case: svn co http://dev.lazaridis.com/base/svn/infra (retrieves some plugins as svn externals, using a specified revision) Manual steps are needed (collected into one script): http://dev.lazaridis.com/base/browser/infra/prepare.py?rev=174 Most of those manual steps _can_ be _eliminated_: http://trac.edgewall.org/ticket/4317 [PATCH] - CORE - Small modifications for loader http://trac.edgewall.org/ticket/4383 CORE - Loader should load single-file plugins after egg plugins http://trac.edgewall.org/ticket/4295 CORE - Provide a mechanism to use custom ini files ... (other tiny tasks, which were not filed) (as said, this is already implemented with the "tracx" plugin, which is essentially a trac based "product", which can be retrieved from the svn in _different_ versions (including dependencies and configuration, thus ready to go) - http://trac.edgewall.org/ticket/4446 CORE - Implement Ability to Provide Trac "Products" (plugin bundles) It is possibly of benefit to address this ticket _after_ the setuptools stuff is moved into trunk. I think it's of benefit to work towards this direction, in order to allow _developers_ to easily fetch a more complete setup directly from svn, with the ability to switch easily between different version. If developer A has a problem and needs a peer-review, other developers can fetch the _complete_ product, activate it, make the tests, and then reactivate their own version again. (3 cmd-lines). . -- http://dev.lazaridis.com/base --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
