On Mon, Dec 13, 2010 at 6:36 PM, Ville M. Vainio <span dir="ltr"><<a href="mailto:vivainio@gmail.com">vivainio@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> Do we have any restrictions on promoting packages that depend on "qt<br>
> experimental"?<br>
<br>
</div>There is no reason to block apps using them from getting promoted. It<br>
was done w/ the old qt4-maemo5 because nokia was going to release Qt<br>
4.6 in pr 1.2 anyway.<br>
</blockquote><div><br></div><div>Waitaminute. There is a lot of history with the -experimental packages. One of the reasons for naming them so was to make it very clear that these are not stable libs and stuff using them should also not be treated as stable. It's seen as the equivalent of 'sid', head, etc. Another thing is that because of the way the promotion process works, applications promoted to testing would always bring (parts of) these experimental builds of 4.7 (later 4.8) with them, corrupting the whole testing process and atomicity of Qt libs. Long story short: keep -experimental in extras-devel and do controlled releases of specific stable updates if necessary (I would say memory bloat is still the lesser of two evils compared to a broken Extras).<br>
</div><div><br></div><div><br></div><div>Best regards,</div><div>Attila</div>