On Dec 15, 7:46 am, Chad Dombrova <[email protected]> wrote: > hi, > i am hoping to convince the maintainers of a project that i follow to switch > from svn to mercurial. they currently use trac so it would be easiest if > they could continue to do so and simply switch to using the tracMercurial > plugin. i just want to make sure that the same access control that exists > for svn will also exist for mercurial. they aren't using anything fancy > now: if you are a registered user, you can commit (after entering a > password), otherwise you cannot. > > i don't know much about trac, but i'm hoping that the access control is > performed by the web server so that we don't have to get involved in the > mercurial acl extension. > > thanks for your time and sorry about the newb question.
Trac is a repository READER with authz support for both svn and mercurial using similar configurations. However, committing to Subversion by the project is done through other means (like apache + mod_dav_svn or whatever), and same with Mercurial repositories that needs to be hosted so that they support getting changesets pushed (google for mercurial serve repository). That said, with Hg being a python app using wsgi frontend app like Trac with many similarities, there would certainly be brownie points for anyone that could make Mercurial plugin a "one-stop-shop" so that the plugin could receive changeset++ requests and Trac permissions and config could be reused... I'm unaware of such a setup, but perhaps anyone have looked into the possibilities? :::simon https://www.coderesort.com http://trac-hacks.org/wiki/osimons -- You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en.
