Policies/Draft/Dependencies Policy

From KDE TechBase
< Policies‎ | Draft
Revision as of 16:31, 27 March 2011 by Odysseus (talk | contribs) (Created page with '== Dependencies Policy == '''DRAFT POLICY''' ''This policy draft is based on a discussion on the k-c-d list.'' This policy outlines the requirements around choosing new depende...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Dependencies Policy

DRAFT POLICY This policy draft is based on a discussion on the k-c-d list.

This policy outlines the requirements around choosing new dependencies for KDE Software in general and the KDE Development Platform in particular.

  • All new dependencies must be advised to the kde-build and kde-packager lists
  • Any changes to KDE Development Platform dependencies (or to KDE Support

projects that the dev platform depends on) to be discussed on k-c-d first

  • Only depend on packages with a stable release
  • Pick dependencies with api/abi guarantees or well managed .so versioning
  • What's our attitude to inherited dependencies at both build and runtime,

i.e. are libraries or services that use GConf/DConf/Glib/etc acceptable?

  • Optional dependencies preferred, try ensure a sensible fallback if not

available

See also:

Maybe additionally there should be a check comparing the "cost" of the new dependency vs. its benefits, i.e. how much feature it brings or how much timne/work it saves compared to doing it self.

Retrieved from "https://techbase.kde.org/index.php?title=Policies/Draft/Dependencies_Policy&oldid=58265"