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... 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. Which makes me wonder how system can cope with several trac-admin/tracd scripts... -- 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 -~----------~----~----~----~------~----~------~--~---
