It did not seem to do any harm when I first tested it with
head. Even the duplicate libs caused no problems as far as I
could tell.
I agree, that might be a nice solution for 0.8 users and
since we'd update the plugin to 0.9 dependant right away, it
would really only be a short term solution.
wdot?
Best regards,
Ferdinand Soethe
Johannes Schaefer wrote:
would it do any harm to deliver the libs twice?
i.e. include in the 0.8 plugin (throw out for the later
versions) and in core?
I haven't had the time to test with 0.8, yet :-(
Johannes
Ferdinand Soethe schrieb:
The pdf-plugin will not work with 0.8 as is because it was decided to
move critical libs from the plugin back into core.
Because of this, the plugin will only work with 0.8 if 0.8 gets patched.
What I haven't tested so far is if 0.8 will work with a locally
deployed plugin that is marked for 0.9?
Or would somebody wanting to use the new plugin with 0.8 also have to
patch the <property name="forrest.version" value="0.8"/>?
Does anybody know or can anybody suggest a better solution?
Best regards,
Ferdinand Soethe
Thorsten Scherler wrote:
On Thu, 2008-02-07 at 23:36 +0000, Ross Gardler wrote:
...
Why are we using skinconf for core plugins? The only plugin that
should
use skinconf is a skin plugin (if it would exist)!
I'm not against breaking the dependency. I'm only against doing it
in 0.3 PDF plugin, released for Forrest 0.8, without warning or good
reason.
Hmm, does the new plugin work in 0.8?
If so can we not release it now and after this raise the version to 0.4
which depends on 0.9. This would allow to incorporate the new properties
system and get rid of duplicate code in the dispatcher.
wdyt?
salu2
