Edward Elhauge wrote:
* Noah Kantrowitz <[EMAIL PROTECTED]> wrote on [2008-02-05 14:03]:
Edward Elhauge wrote:
Hi,

I just set up my first Trac project this week and have some
setup questions. (I have a lot of general software engineering though).

First:
   Does the latest version (0.11) have the ability to edit the
   Ticket description? Or are they immutable as they are in the
   version I have (0.10.4-2)?
They are editable in either version. You need TRAC_ADMIN permissions in both.

Great. That worked like a charm. Takes some of the pressure off of me
to upgrade to the latest and greatest.

The only feedback I'd have is that an Edit button would be nice so that
the Change Properties -> Description textbox section wouldn't take up
so much room. Alternatively a read-only view of the ticket, with all of
it's comments, would be solve the same problem. I envision bringing a
stack of open tickets to a project meeting and going over them one at
a time to see what it would take to close them.
This is a hard issue. A plugin to make a single page or PDF from a query/report would be welcome by many people I bet. I just haven't seen one. If your SQLfu is strong you can probably make a report to simulate it, but that is beyond me.
I got around that by creating a special admin user for myself to do
the revision work. For printing off the Tickets I just log in with
my non-admin user ID.

Second:
   How does easy_install interact with the Debian package system?
   I have easy_install / python-setuptools Ver 0.6c6-1

Problem:
   I set up on an Ubuntu workstation and will eventually migrate
   Trac to a Debian system. Either way it's the Deb package system.
   When I installed Trac initially I installed a bunch of the
   dependencies (Genshi, SQLite, etc) via the Deb package system.
   Then using easy_install I installed Trac. Unfortunately, when I
   did that the egg was downloaded but a lot of the linking and
   copying outside of the egg didn't seem to happen. I then installed
   Trac 0.10.4-2 via apt-get and I managed to get a working version.

[...]

For 0.11 all files are kept bundled inside the egg. You can use the copystatic subcommand of trac-admin to collect all the static files if you want to serve them with Apache or something else (not important for a small, personal system).

Well yes I do need to serve up with Apache. I'm using Trac to
communicate about three projects with about 20 people all told.
Plus misc sys integration work.
No, you don't. Trac has an internal chrome serving system that will work fine for you. The only reason to bother with copystatic is when you start talking about 100s of users, not 10s.
From further research it seems like easy_install keeps it's
own private version of Genshi / Pygments, etc, that stays
out of the way of apt-get installed Python, ideally.
A lot of people seem to have problems making their system work
like that. Now that I have a good working apache version I
should be able to get a 0.11 easy_install version up.
Its not private per se. easy_install (or just python setup.py install) installs the egg into your site-packages folder just like apt or rpm would. Python has a clear divider between core and site libraries, so they generally play nice. If you want to keep things more separate so as to not clutter the site-packages folder with non-apt libraries, check out virtualenv.

--Noah

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to