<div class="gmail_quote">On Fri, Feb 17, 2012 at 18:29, Phil Blundell <span dir="ltr"><<a href="mailto:philb@gnu.org">philb@gnu.org</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">On Fri, 2012-02-17 at 18:14 -0200, Otavio Salvador wrote:<br>
> On Fri, Feb 17, 2012 at 18:11, Phil Blundell <<a href="mailto:philb@gnu.org">philb@gnu.org</a>> wrote:<br>
> We seem to be going in circles here but, to go back to what I<br>
> said at<br>
> the beginning, why can't you use the existing run-postinsts<br>
> recipe<br>
> rather than adding a new script?<br>
><br>
><br>
> My image didn't end with it installed. I did a very small image and I<br>
> expect that independently of what I choose, rootfs behave right.<br>
<br>
</div>Ah, I see. Yes, that's a fair point. Maybe rootfs_ipk itself should<br>
inject ${ROOTFS_PKGMANAGE_BOOTSTRAP} into the image if it notices that<br>
there are postinsts which require running and no other package manager<br>
is installed. I think it would be better not to have multiple scripts<br>
doing the same thing if we can avoid it, otherwise you end up having to<br>
fix things like ordering issues in all of them independently.</blockquote><div><br></div><div>Not easy to do because it might not have been built before.</div><div> </div></div>-- <br>Otavio Salvador O.S. Systems<br>
E-mail: <a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a> <a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a><br>Mobile: +55 53 9981-7854 <a href="http://projetos.ossystems.com.br" target="_blank">http://projetos.ossystems.com.br</a><br>
<br>