Well, the decision to base Trac on Python makes it agony for those of
us who want to do the install. I installed Trac on a windows box and
loved Trac. However, that was a POC. Now that we want to put it on a
Unix server I find it's almost impossible. The stupid ClearSilver
problem is impossible to fix. You google the problem and get back the
same non-working advice.
Trac will succeed as well as the desktop Unix has succeded
(Not!)--at this rate. Personally, if I were on your Trac team I would
do anything I could to make the installation instructions unified and
simpler. Instead, you get referred to 10 different websites, each with
contradictory advice--and in the end--for Unix at least--it doesn't
work!
Now, I know the reply to this will probably be a muted "F*** you".
I accept that. I just find it amazing when tools that are purported to
be ready for prime time are so impossible to install.
On Oct 29, 3:07 am, Rainer Sokoll <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 29, 2007 at 05:10:01AM -0000, Devon wrote:
>
> > Except I don't have a windows server. Not to be rude but this is the
> > reason I still have not learned anything about *nix, anytime I ask
> > questions people keep telling me to turn around and go back where I
> > came from (Windows)... I want to learn but everytime I read a
> > documentation on something for *nix it does not get very detailed (I'm
> > assuming thats because there are so many versions of *nix)...
>
> Go to your local book store and ask for a book that targets on your
> flavour of *nix, or your Linux distribution.
>
> > I've
> > looked through google for sites that may help me (including the
> > subversion.tigris.com)
>
> If you really have no idea about *nix, the this is a bad idea. Nearly
> all *nix related resources in the internet require at least a basic
> understanding of *nix.
>
> > and end up getting more confused. Which at the
> > same time I am afraid that I'll mess something up and not know how to
> > fix it...
>
> You may start with a virtualized installation. There are vmware and co.
> (namely virtualbox).
> Install your favourite distro into a virtual machine (hint: use bridged
> networking, no NAT). You can make snapshots at any time, so it is easy
> to roll back any changes you made to your Linux.
>
> Regarding trac: Trac is pure python, so from a technical point of view,
> there are no big differences between a windows trac and a *nix trac.
> Just tell your OS where to find the shared libraries, and you are set.
> But ask yourself: What is your reason for trac? One great thing with
> trac is its interface to subversion, but it is perfectly OK to run a
> trac without subversion; you can also use trac as a wiki only - it all
> depends on your requirements.
> But trac without subversion is only half the fun :-)
>
> Rainer
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
