[dev] Horde_Kolab_Format and test unit

[Remi Collet]

Hi,

I'm working on Packaging Horde_Kolab_Format.

In the git tree, in lib/Horde/Kolab/Format.php

    const VERSION = '@version@';

So the test suite run there works.

In the published tarball

    const VERSION = '2.0.3;

So test fails with , for exemple.

2) Horde_Kolab_Format_Integration_PreferencesTest::testOverwrite
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
   <sensitivity>public</sensitivity>
-  <product-id>Horde_Kolab_Format_Xml- at version@ (api version:
2)</product-id>
+  <product-id>Horde_Kolab_Format_Xml-2.0.3 (api version: 2)</product-id>
   <application>Test</application>
   <pref>test</pref>


I'd like to understand how this  is changed.
Usually it should be done at install time (using a pear task).
It seems it is done at release time (before the tarball is created)

In all case, shouldn't the @version@ in test unit change at the same
time (so, also having 2.0.3 in the unit test)

Thanks for any explanation
Remi