|
From: Josef W. <Jos...@gm...> - 2005-11-15 16:45:24
|
On Tuesday 15 November 2005 16:14, Nicholas Nethercote wrote: > On Tue, 15 Nov 2005, Josef Weidendorfer wrote: > > > I plan to release Callgrind both for VG 3.0 and VG 3.1 as one package. > > Why? Getting the automake/autoconf stuff right is hard enough... why make > it even more difficult for yourself? :) I do not want to do maintenance releases for a "Callgrind/VG 3.0". E.g. Callgrind 0.9.12 supports all stable VG releases from 2.0. This proved useful in the past. VG30 vs. 31 is special, because of the move to static linked tools. But regarding the tool code, it is not much difference, so I really want to keep one package. As long as it works, this seems to be the best way. If you look at the mailing list, there often are support queries for older VG releases, coming with some distro. E.g. if someone with Suse 10.0 is interested in Callgrind, he does not have to update to VG 3.1 before running newest Callgrind. Josef |