Packaging: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732014-01-17T15:09:32ZOpen Source Collaboration Platform
Redmine Tasks #1720 (New): Fix rstconverters packaginghttps://code.cor-lab.de/issues/17202014-01-17T15:09:32ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>We currently have two distinct version of rst converters. One for humavips, one for amarsi depending on the selected dependencies. This does not scale well and is weird to maintain. We somehow need to find a core set of converters and dependencies or some other solution where we only have ONE version of this package + potential add ons.</p> Tasks #1685 (New): Create Debian package for rsb-javahttps://code.cor-lab.de/issues/16852013-12-11T23:47:01ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deTasks #1560 (New): Delayed package uploadhttps://code.cor-lab.de/issues/15602013-07-12T11:55:25ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Change debian package server deployment to a nightly strategy so that there is more time during development days to fix packages before they end up at end user computers.</p>
<ol>
<li>For this purpose, remove the package server upload from the existing debian package jobs</li>
<li>Add new jobs which get the latest stable debian package from the packaging jobs via copy artifacts and upload them to the server at a nightly basis.</li>
</ol> Bug #1454 (Feedback): Check 'vagrant' for building release VMshttps://code.cor-lab.de/issues/14542013-03-25T13:56:25ZAnonymous
Check <strong>Vagrant</strong> <a class="external" href="http://www.vagrantup.com/">http://www.vagrantup.com/</a> for (continuously) building virtual machines for releases. It is based on simple control files, and
<ul>
<li>downloads latest ubuntu release</li>
<li>installs packages</li>
<li>builds vm image</li>
</ul>
<p>(available for linux, mac and windows)</p> Bug #1041 (New): Comply to Debian Policy Manualhttps://code.cor-lab.de/issues/10412012-06-27T08:52:40ZAnonymous
<p>We should try to comply to the basic key points of the (substantial) Debian Policy Manual:<br /><a class="external" href="http://www.debian.org/doc/debian-policy/">http://www.debian.org/doc/debian-policy/</a></p>
There are lot of recommendations and requirements regarding the structure and contents of debian packages, eg.
<ul>
<li>Package naming and versioning</li>
<li>Content (licensing information, readme, changelog, ...)</li>
<li>Required metadata (author, maintainer, ...)</li>
<li>Description of contained libraries (shlibs file)</li>
<li>and much, much more ...</li>
</ul> Tasks #1005 (New): Create lib*, *-dev and *-bin packages and sort out some complicance issueshttps://code.cor-lab.de/issues/10052012-06-18T14:03:54ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
For typical C[++] libraries, we should have
<ul>
<li><code>libname</code></li>
<li><code>libname-dev</code></li>
<li>and optionally <code>name-bin</code><br />packages</li>
</ul>
<p>We should adhere to naming conventions in package and file names.</p> Tasks #1004 (New): Create Debian packages for rsb-python, rst-pythonhttps://code.cor-lab.de/issues/10042012-06-18T14:03:36ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deTasks #950 (New): Create packages for documentationhttps://code.cor-lab.de/issues/9502012-03-15T00:44:32ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Affected projects
<ul>
<li>rsb/manual</li>
<li>rsbag/manual</li>
<li>rst/manual</li>
<li>rsb-test/manual</li>
</ul>
<p>For Debian/Ubuntu these should probably be something like <code>rsb-doc-0.7</code>.</p> Feature #230 (New): Think about wrapper script or extension for spread daemonhttps://code.cor-lab.de/issues/2302011-03-20T13:47:32ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>If we further use Spread we should either write a wrapper script that removes /tmp/<port> or directly add this to the spread dameon's source code.</p>