Emmanuel Blot wrote:
> Hi,
>
> It seems that the commit hook scripts for SVN are actively supported.
> I think it would make sense to move them out of the contrib/ directory
> that contains files which are explicitely described as with weak or no
> support.
>   

Ok to clarify the status...

> An alternative would be to move the unsupported script to trac-hacks
> or a MacroBazaar-like page.
>   

But yes, I rather keep them in place for now and move the unsupported 
scripts to contrib/unsupported as a kind of "deprecation warning" and 
maybe even remove that unsupported folder before the next release.

This will concern:

contrib/unsupported/bugzilla2trac.py 
contrib/unsupported/emailfilter.py
contrib/unsupported/sourceforge2trac.py

> I think the status of the commit hook scripts is quite confusing for now
>   

Those scripts should perhaps be packaged with a "Subversion" module one day.
I don't know the exact form this could take, but that would be a kind of 
bundled plugin that would be installed by default but only activated if 
a svn repository is used.

E.g. that could be in a new toplevel folder tracext:

tracext
tracext/versioncontrol
tracext/versioncontrol/subversion
tracext/versioncontrol/subversion/setup.py
tracext/versioncontrol/subversion/svn/fs_backend.py (moved from 
trac/versioncontrol/svn_fs.py)
tracext/versioncontrol/subversion/hooks/trac-post-commit-hook

-- Christian

--~--~---------~--~----~------------~-------~--~----~
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