23 Aug
2013
23 Aug
'13
7:30 a.m.
Hi Tim,
Darrell, Slavek,
thanks all for your feedback. Slavek's comments explain the problem I was
facing.
I am using the sources from the GIT repository for TDE and TDE-packaging.
In December/January 2013 (the last time I had enough time to build TDE) I
had no major problems building TDE.
Last week when I tried again, I run into this dependency problem and after
checking with the nightly build website I found the differences in the
package version number I mentioned in my first message. So as Slavek said,
the scripts used to generate the .deb packages automatically add the new
version number and that's why the nightly build tarball builds to a 14.0.0
version instead of 2.3.22. So I will just have to do the same.
-- Unless I am doing something wrong or missing something in the building
process (which could well be the case :) )--, IMO the TDE-packaging and TDE
GIT repository should be synchronized, by either updating the package build
scripts or by adding the scripts that are used by the autobuild system.
At the moment if a Debian user tries to build TDE package-by-package from
the GIT repository using the current TDE-packaging GIT repository, he/she
will run into dependency problems like the one I mentioned.
Cheers
Michele
Constantly updated versions in tde-packaging to me does not seem like a good
idea. Not only would it generate a lot of unnecessary changes, but also would
not guarantee that the version actually corresponds to the current state of
appropriate git module.
Sense might have if version will be updated at the time of release of the new
final version => be labeled using git tag. However, this does not solve your
trouble. What could you help if I gave you my script for generating source
deb packages...
Slavek