On 11/04/07, <b class="gmail_sendername">Mario Limonciello</b> <<a href="mailto:mario.mailing@gmail.com">mario.mailing@gmail.com</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;">
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><span class="sg"><br>Mario<br></span></blockquote></div><br><br>Hi Mario,<br><br>Although I have currently enabled processor optimisations that is not the underlying reason I like to use trunk. Essentially I want the features available in trunk and like to be able to help test. eg. With the upcoming record multiple muxes from a single transport stream, I would like to be able to help test the functionality of this code and offer any feedback I can.
<br><br>What I was originally thinking was of a meta package to help those that want to compile from source to get their environment setup as quickly/easily as possible. The actual "configure, qmake, make, make install" really isn't that time consuming.
<br><br>It would be interesting to hear from some of the devs their thoughts, do they think that nightly SVN builds (and deb packaging) would help or hinder their development process.<br><br>Cheers,<br><br>Roo.<br>