<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 2, 2013 at 10:04 AM, Otavio Salvador <span dir="ltr"><<a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb adM"><div class="im">On Wed, Jan 2, 2013 at 12:51 PM, Christopher Larson<br>
<<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>> wrote:<br>
> On Wed, Jan 2, 2013 at 4:53 AM, Shakeel, Muhammad<br>
> <<a href="mailto:muhammad_shakeel@mentor.com">muhammad_shakeel@mentor.com</a>> wrote:<br>
>><br>
>> addtask do_archive_scripts_logs after do_package_write_rpm<br>
>> +addtask do_archive_scripts_logs after do_package_write_ipk<br>
><br>
><br>
> This will cause problems for anyone trying to do builds without package_ipk<br>
> at all. I'd suggest using anonymous python to add the appropriate package<br>
> dependencies based on what tasks actually exist.<br>
<br>
</div></div>Uh? the only exception for it would be deb, right?</blockquote></div><br></div><div class="gmail_extra" style>Yes, and?</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>-Chris</div>
</div>