osimons kirjoitti: > > On Jul 1, 12:47 pm, Jani Tiainen <[EMAIL PROTECTED]> wrote: >> Alec Thomas kirjoitti: >> >>> This occurs because Trac's static content and templates are shipped >>> within the egg. They must be accessible for normal file access and >>> thus the egg must be unpacked, or cracked open, if you like. >> I don't get it. >> >> Wasn't setuptools meant for using simple .egg files (at least most of my >> plugins are in zipfiles, even they contain shared data) and in runtime >> setuptools extracts plugins (and staticdata) to some temporary directory >> (egg-cache). >> >> So there is something incorrect in above statement. >> >> Actually now that I look my plugins only EGG that is installed as >> extracted is Trac itself for some reason... > > Trac setup.py uses the zip_safe = False flag to ask setuptools to > extract when installing. > >> Altough that shouldn't be necessary since to get static resources out - >> user is required to run "deploy" command to extract static data from .egg. > > Templates are also static resources that need to be accessed - they > don't get 'deployed'.
How they get accessed from zipped eggs? Like Timing and Estimation that I've installed, it's single egg file, it contains at least one template and still it works, so there must be way better explanation. Maybe Trac does something for plugins that are beyond of capabilities of setuptools so plugins don't need to be extracted? >> Which makes me wonder how system can cope with several trac-admin/tracd >> scripts... > > Quite simple actually - there can only be one... The scripts are very > simple though, and just loads everything from the active egg (as seen > in site-packages/easy_install.pth). But how you spesify which trac to run... Let's think that I've two versions in my system: 0.11-stable to run production and 0.12-dev now how I can tell which one to run? Since this new "deploy" was meant for side-by-side installation of several versions of Trac... Quoting Noah about that one: " In short: we cannot have a single global data folder like that anymore since to be compliant with the spirit of setuptools we need to allow things like multiple versions installed concurrently. In fact we cannot install anything outside the egg. trac-admin deploy will extract/generate the content you need, and since it is manual, hopefully you won't overwrite one version's data with another :) " Deploy really doesn't extract templates, which actually were part of old "/usr/share/trac" tree. -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
