I am upgrading Debian Squeeze systems from TDE 3.5.12 to 3.5.13.
The upgrades seem to work fine omitting the following packages: gcc-4.5-base 4.5.2-8ubuntu4 i386 libgcc1 1:4.5.2-8ubuntu4 i386 libgfortran3 4.5.2-8ubuntu4 i386 libgomp1 4.5.2-8ubuntu4 i386 libstdc++6 4.5.2-8ubuntu4 i386
I am loathe to install non-Debian versions of these packages in case they cause problems with other Debian software, either now or in future. Is there any reason why Trinity needs to replace such critical packages?
Thanks,
--Mike Bird
I am upgrading Debian Squeeze systems from TDE 3.5.12 to 3.5.13.
The upgrades seem to work fine omitting the following packages: gcc-4.5-base 4.5.2-8ubuntu4 i386 libgcc1 1:4.5.2-8ubuntu4 i386 libgfortran3 4.5.2-8ubuntu4 i386 libgomp1 4.5.2-8ubuntu4 i386 libstdc++6 4.5.2-8ubuntu4 i386
I am loathe to install non-Debian versions of these packages in case they cause problems with other Debian software, either now or in future. Is there any reason why Trinity needs to replace such critical packages?
Thanks,
--Mike Bird
That looks like a side effect of having to build Trinity on a newer version of gcc than Squeeze provides. You shouldn't have to install the upgraded gcc if you don't want to.
Tim
On Wed November 9 2011 15:43:18 Timothy Pearson wrote:
That looks like a side effect of having to build Trinity on a newer version of gcc than Squeeze provides. You shouldn't have to install the upgraded gcc if you don't want to.
OK, we've now removed all of trinity-builddeps-v3.5.13 except the following: hal-trinity imlib-base imlib11 launchpad-integration libakode2 libcaldav libcarddav libdbus-qt-1-1c2 (which we use with Lenny's kdebluetooth)
Maybe sometime builddeps could be split into deps and builddeps. Sorry, I don't have the time to help right now.
Thank you Tim and friends for Trinity,
--Mike Bird