yuppie wrote at 2006-7-14 11:30 +0200:
> ...
>> We have a Zope version where package resources (such as skins)
>> can come together with the package from a zip archive
>> (this is a function similar to the newer "egg" Python function).
>> We identify such resources via "pypackage" urls which have the form
>>    pypackage:package/path
>> Here "package" is the full package path (e.g. "path.to.some.package").
> ...
>Please note that in CMF 2.1 this is just a registry key for looking up 
>DirectoryInformations. It is no longer used for looking up the 
>filesystem resources directly.
>The identifiers discussed here are useful for direct lookup, but IMHO 
>they are overkill for registry lookup.

When I remember right, the original question was how these
keys are represented externally -- in a GenericSetup profile.

And there, such a representation may well be adequate...

Zope-CMF maillist  -  Zope-CMF@lists.zope.org

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to