Dear all, I would like to make a list of 3rd party dependencies that we include. Do we already have such a list? In future major releases, I would propose that the release manager consider updating these dependencies before any alpha release, and perhaps before any beta. Actually, if others prefer, I'm fine with updating them even before an rc; but even in this case we can reduce the risk of an incompatibility by also remembering to update them before an earlier pre-release so I think collecting this list is still useful.
Ideally, we would include the following information in such a list:
dependency name:
URL to check for new version:
loose guidelines for updating: [e.g. only point releases; only before
alpha; only if we need a newer feature]
But I will be happy if we just make a list of names.
The following is useful:
ls 3rdparty/
But I think there may be others?
So far on the list I see:
boost
evince_sync
hunspell
iconv
mythes
xvkbd
zlib
For example, since xvkbd is only used for our tests, I think we could
update it at any time. Although in theory the keytests would be robust
enough that we would encourage packagers to run these tests so maybe we
should be more careful. But since in my opinion the tests are too
fragile we should not push packagers.
What else should we add to the list?
Scott
signature.asc
Description: PGP signature
