Christopher Lenz wrote: > Hi Luis, > > Am 19.10.2006 um 01:28 schrieb Luis Matos: > >> i am using the debian package and i see that /etc/trac is empty. >> >> I want to full customise the interface for my company, but there is no >> place where we can change all we want. >> >> I filled a bug in debian about this, against the trac package[1] and i >> am in the will to provide some advice, or opinion if the project is >> interested in it. >> >> Debian maintainers have no will to diverge much from your upstream >> version, so i subscribed to the list to try to propose this in the >> riht >> place. >> >> My point is to create a /etc/trac with >> >> custom css ( to overlap trac css) >> /htdocs (pictures, etc) >> /roadmap default options >> default trac.ini >> default wiki pages. >> >> some of this is available in /usr/share/trac but they are in the wrong >> place. >> >> What do you say about this? >> >> For some things i think that is possible changing only the >> siteconfig.py >> (or setup.py in the package), do you confirm (for htdocs)? >> >> what abou the rest? >> > > Good timing for your message, as we're going to change these things > for 0.11 when moving to setuptools for installation. > > siteconfig.py is going to be removed, and Trac will no longer install > data files in /usr/share/trac. Instead, the default set of templates, > wiki pages and wiki macros will be stored inside the Trac package in > site-packages, and will no longer be intended to be overwritten by > admins/users. >
nice > However, you will still be able to configure things like shared > templates and wiki pages directories. This would be done as options > to the "trac-admin initenv" command, for example: > > trac-admin /var/trac/proj initenv \ > --templates /etc/trac/templates \ > --wiki-pages /etc/trac/wiki-pages > about trac admin. It's good for who has access to the machine. Normally, with multiple projects project admins don't have it. Although, using trac-admin to create the project is not straight forward, especifying several variables. for overdue that, my propose is to install in /etc/trac some files to configure that that will overdue the trac files. > These command-line options are stored as regular config options in > the projects trac.ini. Note that Trac would not automatically create > those directories on installation, that'd be the responsibility of > either the admin or the distro package. > Abou trac.ini. It is easier to have a full trac.ini, or some other file, that would be easy to setup, again, as a config file, it should be in /etc/trac. > Now, to make handling of multi-environment installs somewhat easier, > I would suggest we inspect a number of environment variables that can > be used to provide defaults. So for example, you could define: > > TRAC_TEMPLATES_DIR = /etc/trac/templates > TRAC_WIKI_PAGES_DIR = /etc/trac/wiki-pages > > Why don't you make a place where the package mantainers could change this. It was siteconfig.py ... is it still? it should be important to define a config dir at install. > and you'd no longer have to specify those when invoking "trac-admin > initenv". > that's the full point > Does that sound reasonable? > > what about default roadmap. Default icons, default css ... > Cheers, > Chris > -- > Christopher Lenz > cmlenz at gmx.de > http://www.cmlenz.net/ > > Best Regards Luis Matos --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
