https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-06-01T12:49:19ZOpen Source Mobile CommunicationsOsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=96992018-06-01T12:49:19Zlaforge
<ul><li><strong>Assignee</strong> set to <i>118</i></li></ul> OsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=152682019-07-18T05:43:00Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>118</i> to <i>fixeria</i></li></ul> OsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=175562020-02-26T23:38:41Zlaforge
<ul></ul><p>I just realized that we still don't have this. It's a bit of a pity. I'm not the debian package expert, but I think we'd probably actually have one debian/ subdirectory for each of the sub-projects, as each of them (virtphy, trxcon, layer23, ...) comes with it's own configure.ac/Makefile.am/etc. anyway.</p>
<p>Or is there a better way? I'm sure one can add tons of overrides in debian/rules and build all of the sub-projects from a single set of packaging rules - but at what advantage? Treating individual sub-directories as separate source packages seems to make more sense to me.</p>
<p>comments, anyone?</p> OsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=175622020-02-27T08:57:18Zosmith
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>I'm sure one can add tons of overrides in debian/rules and build all of the sub-projects from a single set of packaging rules - but at what advantage? Treating individual sub-directories as separate source packages seems to make more sense to me.</p>
</blockquote>
<p>Ack. The less complex, the better.</p> OsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=175642020-02-27T10:23:27Zpespin
<ul></ul><p>Well to me the question would be: why do we have several autofoo projects all around in osmocom-bb? That's the case right? I always found that quite annoying and fixing that would also allow for 1 and only 1 debian/ dir ("to rule them all").</p> OsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=175652020-02-27T13:22:30Zlaforge
<ul></ul><p>On Thu, Feb 27, 2020 at 10:23:28AM +0000, pespin [REDMINE] wrote:</p>
<blockquote>
<p>Well to me the question would be: why do we have several autofoo projects all around in osmocom-bb? That's the case right? I always found that quite annoying and fixing that would also allow for 1 and only 1 debian/ dir ("to rule them all").</p>
</blockquote>
<p>Because it's rerally a collection of independnet projects. THere's zero code shared between<br />'layer23' and 'trxcon', for example. So why build all of them all the time in some integrated<br />way if they have no relation? And particularly once you go to firmware builds, you end up<br />with a non-autotools crosscompile project that has no relation to the rest.</p>
<p>The onlything all those programs have in common is that they work on the MS side of the Um<br />interface, or in the Um interface itself. Some are embedded code for ARM7TDMI, some<br />are python, some are C, ...</p> OsmocomBB - Feature #2379: package as .debhttps://osmocom.org/issues/2379?journal_id=175662020-02-27T14:39:11Zfixeria
<ul><li><strong>Assignee</strong> deleted (<del><i>fixeria</i></del>)</li></ul>