|
From: Josef W. <Jos...@gm...> - 2004-02-19 15:05:58
|
Hi, as I have a bug report from a Calltree user for debian/unstable, which obviously only includes VG 2.1.0, I have a question... Was VG 2.1.x supposed to be released in distributions at all? Of course, we can't prohibit it, but should suggest a stable version to be distributed (i. e. 2.0.x, 2.2.x,...). My assumption was that VG 2.1.x is unstable and more or less kind of a better CVS-Snapshot. This is reflected by the Skin/Tool-API version number, which is *not* incremented in the 2.1.x series. So I never had in mind to support a 2.1.x release for Calltree, and that's because of the tool-API versioning policy not even possible in a sane way. But if VG 2.1.x is the only Valgrind version delivered with a distribution, you can't install Calltree, because there is no version for VG 2.1.x. Is it OK to suggest to the Debian guys to downgrade to VG 2.0.x ? (Of course, they optionally can include 2.1.x as separate package that is not conflicting with the stable VG package). Josef |
|
From: Nicholas N. <nj...@ca...> - 2004-02-19 15:12:27
|
On Thu, 19 Feb 2004, Josef Weidendorfer wrote: > Is it OK to suggest to the Debian guys to downgrade to VG 2.0.x ? > (Of course, they optionally can include 2.1.x as separate package that is not > conflicting with the stable VG package). Seems reasonable to me. N |