Andreas Tille pushed to branch master at Debian Med / community / policy

Commits:
f3283474 by Andreas Tille at 2018-02-14T13:49:37+01:00
Spelling Bio-Linux

- - - - -
6820432a by Andreas Tille at 2018-02-14T13:49:37+01:00
Package template was moved to Git as well

- - - - -


1 changed file:

- policy.xml


Changes:

=====================================
policy.xml
=====================================
--- a/policy.xml
+++ b/policy.xml
@@ -274,7 +274,8 @@ Host *.debian.org
 <command>cd</command> <filename class="directory">package</filename>
 <command>git init</command>
 <command>gbp import-orig</command> <option>--pristine-tar</option> 
<filename>/path/to/package_version.orig.tar.gz</filename>
-<command>svn export 
svn://anonscm.debian.org/svn/debian-med/trunk/package_template 
debian</command></programlisting>
+<command>git clone 
https://salsa.debian.org/med-team/community/package_template.git 
/tmp/package_template</command>
+<command>mv /tmp/package_template/debian . ; rm -rf 
/tmp/package_template</command></programlisting>
                                </para>
                                The above steps will create a repository with 
the appropriate layout for <command>gbp buildpackage</command>, with three 
branches:
                                <literal>master</literal> (where the Debian 
development will happen),
@@ -517,7 +518,7 @@ rm ../*_source.changes</programlisting>
                <sect2 id="derivatives">
                        <title>Derivatives working together with Debian 
Med</title>
                        <para>
-                               Debian Med is proud that derivatives (like for 
instance <ulink 
url="http://environmentalomics.org/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>&lt;upstreamversion&gt;-0&lt;derivativename&gt;&lt;derivativerevision&gt;</code>
 (which is the versioning scheme usually used by Ubuntu).
+                               Debian Med is proud that derivatives (like for 
instance <ulink 
url="http://environmentalomics.org/bio-linux/";>Bio-Linux</ulink>) are profiting 
from our work inside Debian and we try to establish strong connections to these 
derivatives.  With Bio-Linux the connection is as strong that a common workflow 
was created where Bio-Linux 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>&lt;upstreamversion&gt;-0&lt;derivativename&gt;&lt;derivativerevision&gt;</code>
 (which is the versioning scheme usually used by Ubuntu).
                        </para>
                </sect2>
                <sect2 id="r-packages">



View it on GitLab: 
https://salsa.debian.org/med-team/community/policy/compare/8692db2c14b0bffa3365b6feeed3811117993bd6...6820432aae831cd548ef6b133a1c5b90e14394bd

---
View it on GitLab: 
https://salsa.debian.org/med-team/community/policy/compare/8692db2c14b0bffa3365b6feeed3811117993bd6...6820432aae831cd548ef6b133a1c5b90e14394bd
You're receiving this email because of your account on salsa.debian.org.
_______________________________________________
debian-med-commit mailing list
debian-med-commit@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-commit

Reply via email to