gmane.comp.version-control.subversion.trac.general

Attn early adopters: disabling components and global config

Hey folks,

I today checked in a change that needs some further explanation:

  <http://projects.edgewall.com/trac/changeset/2335>

In particular, this changes the way how plugins/components are  
enabled/disabled for a Trac environment. Where you'd previously use a  
[disabled_components] section in trac.ini to specify which components  
should be disabled, you now use a [components] to both enable and  
disable components.

Only the components in the "trac" package are enabled by default. You  
can still disable specific builtin components in trac.ini, for example:

   [components]
   trac.ticket.web_ui.UpdateDetailsForTimeline = disabled

would disable the "Ticket details" provider for the timeline.

You can also disable complete modules/packages, for example:

   [components]
   trac.versioncontrol.* = disabled

would disable all the functionality related to version control (the  
repos browser, changesets, etc). Note that the wildcard at the end is  
now required! Wild cards are only allowed at the end of the option name.

But the big change is that plugins, i.e. Python code outside the

(Continue reading)

headers

Sergey A. Lipnevich | 9 Oct 00:50

Re: Attn early adopters: disabling components and global config

Christopher Lenz wrote:

> file comes in.  You can now specify global options in 
> $prefix/share/trac/conf/ trac.ini (you need to create the file 
> yourself for the time being).  These global options are inherited by 
> all the Trac environments.
>
Would /etc/trac.ini be a better location? I package Trac for Source Mage 
GNU/Linux, and we prefer to keep configuration in /etc. In this case, 
I'd ideally have to set up a symlink for 
$prefix/share/trac/conf/trac.ini to point to "real" file /etc/trac.ini. 
While it's an OK solution to satisfy standards and keep Trac happy, I'd 
rather not have to alter preferred package layout.
Keep up an outstanding work,

Sergey.

headers

Matthew Good | 9 Oct 01:11

Re: Attn early adopters: disabling components and global config

On Sat, 2005-10-08 at 18:50 -0400, Sergey A. Lipnevich wrote:
> Christopher Lenz wrote:
> 
> > file comes in.  You can now specify global options in 
> > $prefix/share/trac/conf/ trac.ini (you need to create the file 
> > yourself for the time being).  These global options are inherited by 
> > all the Trac environments.
> >
> Would /etc/trac.ini be a better location? I package Trac for Source Mage 
> GNU/Linux, and we prefer to keep configuration in /etc. In this case, 
> I'd ideally have to set up a symlink for 
> $prefix/share/trac/conf/trac.ini to point to "real" file /etc/trac.ini. 
> While it's an OK solution to satisfy standards and keep Trac happy, I'd 
> rather not have to alter preferred package layout.

Well, we were just talking about this on IRC since I brought up
preferring /etc/trac.ini as well, although unfortunately there doesn't
seem to be a nice way to handle this with distutils, so it can't be
handled in a portable manner.  So, for now I think it will need to be up
to the packagers to relocate the file as necessary for their
distribution.

--

-- 
Matthew Good <trac@...>