victoria wrote:
> Hi!
>
>
>> Yep, the second installer worked. It's a bit unusual to end up with
>> 32-bits software installed below C:\Program Files, though (should be
>> "C:\Program Files (x86)" on Windows x64 systems).
>>
>
> We have found some issues (in other application packages) with '(' and
> ')' characters as not all applications support that. That is why we
> setting "C:\Program Files" by default as the installation directory.
>
>
OK, no big deal, I'm not a Windows purist anyway :-)
>> Authentication was correctly set up, though for a more effective start,
>> one would expect that the user specified in the installer would end up
>> having the TRAC_ADMIN permissions, so that you can start right away
>> configuring your environment.
>>
>>
>
> Ok. You are referring to this: "trac-admin /path/to/projenv permission
> add bob TRAC_ADMIN". We'll add this, it makes sense
>
>
>> The README.txt file still talks about the WebAdmin plugin as an example
>> - bad example, as you should *not* install the 0.10.x WebAdmin plugin in
>> Trac 0.11.x, which has the admin panels built in.
>>
>>
>
> I missed that. Any suggestion? Do you know which is the Trac plugin
> that people use more?
>
Maybe the account manager plugin?
(http://trac-hacks.org/wiki/AccountManagerPlugin).
>
>> A part from those minor glitches (which I think are easy to fix), it
>> works great, mod_python is correctly configured.
>> In addition, it would be great if HTTP access to the svn repository
>> would be configured as well, so that people could start commit code to
>> their project right away ;-)
>>
>>
>
> Are you referring to configuring apache with mod_dav? The reason why
> we don't configure it is because you can browse your code through the
> Trac interface but I may be missing something...
>
mod_dav_svn.so, yes. Browsing is certainly best achieved using Trac, of
course, but some people prefer to use the http:// protocol for checking
the code in and out, in preference to the svn:// protocol (I've seen
that you provide the scripts to install svnserve.exe as a service).
>> I also like the very clean way everything is organized below "C:\Program
>> Files\BitNami Trac Stack", but apparently it's in part theoretical, as
>> the actual install of python Lib and DLLs is duplicated below
>> apache2/bin. If one wants to upgrade Trac manually (hint for fellow Trac
>> developers, try out 0.12dev!), then the .eggs, .pths and all that have
>> to end up *there*).
>>
>>
>
> We try to keep the same structure for all distributions (linux, osx
> and windows). However, on Windows, duplicate these folders is
> necessary if we want to avoid creating environment variables and keep
> clean the user environment (as mentioned earlier we don't modify the
> user environment variables).
>
Too bad...
>> Hope you'll find the advice helpful. On my side, I'll use the BitNami
>> Trac as a nice test environment for mod_python 3.3.1 on Windows ;-)
>>
>>
>
> Ah! Enjoy it :) And thanks! Really appreciated your feedback. We'll
> start working on the
> improvements :)
>
You're welcome. I think we now have an answer to give to people
complaining about the lack of a full featured installer on Windows ;-)
Some ideas for a future v0.12 stack: Python 2.6, mod_wsgi 3.x instead of
mod_python, and, why not, Mercurial and TracMercurial, in addition to
Subversion ;-)
-- 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.
