> Perhaps this can be solved by custom (+ temp) deployer,
> which would create capabilities from those exports,
> but would just say import-all for imports.
No shit sherlock...Especially when thats what is being done now.
We hide this packages outcome/export in non-plugable way inside
VFSCLPolicy, with explict scanning.
Where here we would simply read a bunch of strings.
Again, optimizing this algorithm doesn't matter if
Well, it's still 9%, which come very cheap if we do/use this