<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 13, 2020 at 8:24 AM Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr">On Thu, 13 Feb 2020 at 17:06, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div class="gmail_quote"><div dir="auto">No, problem is that if One wants to use opkg backend then rpm drags along but apt or dpkg don’t</div><div dir="auto"><br></div><div dir="auto">Even if test is made to pass rpm will be dragged into</div><div dir="auto">Images which is not desired</div></div></div></blockquote><div><br></div><div>We can modify the rpm packaging so that only the library from rpm that libresolv links with, but not the executables or other libraries are in the image. Would you be ok with that?</div></div></div></blockquote><div dir="auto"><br></div><div dir="auto">This still sneaks in pieces of rpm into distros where rpm is not needed so better would be to retool dnf to not demand rpm support in libsolv and break the dependency chain. Opkg is usually sought for small systems and last thing we want is unneeded dependencies </div><div dir="auto"><br></div><div dir="auto">I would rather use the OE configuration powers as such but I am not opposed to such a solution</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><div><br></div><div>Alex</div></div></div>
</blockquote></div></div>