Roo,<br><br>I have toyed with the idea of doing another repository that will do nightly svn checkouts and builds, but then that introduces interoperability problems if people start to mix and match, or decide that svn isn't stable enough for them.
<br><br>Before I think too much more into the design required for nightly svn builds into debs, what are you looking out of building from source? The fact of compiling towards a particular processor, or just the newer packages? If the latter, I'll think more about the process necessary. If the former, then there is little that will be doable with regard to deb generation.
<br><br>Mario<br><br><div><span class="gmail_quote">On 4/9/07, <b class="gmail_sendername">Roo</b> <<a href="mailto:roo.watt@gmail.com">roo.watt@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q">On 10/04/07, <b class="gmail_sendername">Mario Limonciello</b> <<a href="mailto:mario.mailing@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mario.mailing@gmail.com<img class="TargetAlertIcon" src="chrome://targetalert/content/skin/new.png">
</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Ben,<br><br>Since edgy release, I have been working with maintenance on the Ubuntu packages.<br><br>I *do* use all the packages that I build on all of my frontends and backends. They do indeed track the 0.20-fixes branch within reason. Due to Ubuntu's release procedure, you won't commonly see updates between the 6 month releases unless something big needs to be updated.
<br><br>Hold off until <span id="st" name="st" class="st">Feisty</span> release to use the packages though. I have one more set of changes coming in that should hopefully be the final resolution to all of the DB issues people encounter due to group membership/misreading of debconf dialogs and such. The version on the packages will be
0.20-svn20070122-0.0ubuntu5.<br><br>Regards,<br><span><br>Mario</span></blockquote></div><br></span>Hi Mario,<br><br>Maybe you could help point me in the right direction...<br><br>I have been considering creating a .deb that is an "empty" (metal) package that installs all the required development libraries for source compilation.
<br><br>The other possibility would be to maintain a list of the package names that are needed to compile, this could be a wiki article and could then be maintained by the community.<br><br>I think the wiki is probably the best way to go as it can be updated easily as trunk changes, eg the new taglib requirement for mythmusic.
<br><br>The other part of the problem is the /etc/init.d/* scripts needed and others scripts. I guess it would be best if we used the scripts that your *.debs use if you don't mind.<br><br>Any thoughts would be appreciated.
<br><br>Cheers,<br><span class="sg"><br>Roo.<br>
</span><br>_______________________________________________<br>mythtv-users mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org<img class="TargetAlertIcon" src="chrome://targetalert/content/skin/insecure.png">
</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users<img class="TargetAlertIcon" src="chrome://targetalert/content/skin/new.png">
</a><br><br></blockquote></div><br>