23 Oct
2013
23 Oct
'13
5:37 p.m.
Dne st 23. října 2013 Michele Calgaro napsal(a):
Doing a full rebuild when binutils gets updated is not
a huge problem
after all, so we could keep the tight dependency if we really need it.
On the other hand this could become an issue for users of Debian Stable
(and Ubuntu I guess) who uses only official TDE releases and not the
nightly builds. If there is an update for Stable, the users would be
unable to update their binutils package until a new TDE release using
the same binutils version is available.
Perhaps a savy solution would be to keep the dependency from bfd off by
default, so the aforementioned users would have no problems if a Stable
update becomes available. We can add a compile option to enable the bdf
dependency, so if we need to debug some nasty bugs we can recompile
everything and work with the enhanced backtrace information.
What do you think?
I believe that a close relationship to binutils is just a minor problem
for users running stable version. It is very unlikely that in the updates
for stable version of Debian/Ubuntu distribution (or backports) will be
updated binutils, which would break dependencies.
The problem is therefore only applies to users who use testing and
unstable distributions. For such versions of distributions is not
possible to release the "final" versions of TDE, because any time
something can go wrong. I assume that users will always have to use
either nightly-builds or preliminary updates for stable TDE branch. As
was my ppa for v3.5.13.x branch.
In any case, if backtraces is good even without the lib bfd, we can turn
off WITH_LIBBFD and remove binutils-dev from tdelibs-trinity build-deps
and tdelibs14-trinity-dev dependencies. To me this seems appropriate.
Slavek
--