Author: tille
Date: 2014-01-03 09:09:51 +0000 (Fri, 03 Jan 2014)
New Revision: 15719
Modified:
trunk/community/website/docs/policy.xml
Log:
Add hint how to do version numbering for derivatives
Modified: trunk/community/website/docs/policy.xml
===================================================================
--- trunk/community/website/docs/policy.xml 2014-01-03 04:59:05 UTC (rev
15718)
+++ trunk/community/website/docs/policy.xml 2014-01-03 09:09:51 UTC (rev
15719)
@@ -582,6 +582,12 @@
Lintian checks are adapted to Ubuntu by setting
the environment as follows: <code>LINTIAN_PROFILE=ubuntu</code>.
</para>
</sect2>
+ <sect2 id="derivatives">
+ <title>Derivatives working together with Debian
Med</title>
+ <para>
+ Debian Med is proud that derivatives (like for
instance <ulink url="http://nebc.nerc.ac.uk/tools/bio-linux";>BioLinux</ulink>)
are profiting from our work inside Debian and we try to establish strong
connections to these derivatives. With BioLinux the connection is as strong
that a common workflow was created where BioLinux developers are injecting
their packaging straight into the Debian Med version control system. To make
sure that there will be no conflicts with the Debian revisions some attention
should be payed to the revision numbering. If the derivative is creating a new
package (either from scratch or an upgraded version) it should get the version
<code><upstreamversion>-0<derivativename><derivativerevision></code>
(which is the versioning scheme usually used by Ubuntu).
+ </para>
+ </sect2>
<sect2 id="r-packages">
<title>R packages</title>
<para>
_______________________________________________
debian-med-commit mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-commit
