26 Jan
2011
26 Jan
'11
5:43 p.m.
On Wednesday 26 January 2011 18:28:13 Timothy Pearson
wrote:
External dependencies (e.g. non-Trinity libraries) stay at the
distribution level.
Yes, you are correct; if it builds against 3.5.12 I will put it into SVN.
However, you will likely find that there are minor tweaks that must be
done to the source code due to slight API changes in the Trinity core.
No, I don't have a list handy at the moment. ;-)
Tim
If you (or another RedHat/OpenSUSE person) want
to do that please feel
free to do so. Personally I use Ubuntu and Debian and am therefore
completely unfamiliar with the RedHat/Fedora/OpenSUSE way of doing
things.
The only thing I would ask is that the packager please send me a
.tar.gz
file that compiles against Trinity 3.5.12 so that I may add the new
application to SVN.
So having tgz and the patches is enough to have it ported to Trinity?
In that case the most of the applications we discussed recently can be
ported.
They build well for the upcoming OpenSUSE 11.4 and if you say Trinity is
source-compatible with KDE 3.5.10, nearly all of them are also compatible
with Trinity.
By the way, what do you do with packages which require external
dependencies
(i.e. those which are part of the distro itself and not included in
Trinity)?
Can such packages be included in Trinity?