<div dir="ltr">Go ahead and do a v2, it was more of a reminder for me.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 18, 2017 at 4:26 PM, Mark Asselstine <span dir="ltr"><<a href="mailto:mark.asselstine@windriver.com" target="_blank">mark.asselstine@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Monday, December 18, 2017 4:07:44 PM EST Derek Straka wrote:<br>
> I also need to look at the UPSTREAM_CHECK_URI for this recipe since it<br>
> isn't finding the latest version and telling me to update the package.<br>
<br>
</span>Odd. Let me know how it goes. If it is easier for you to make the changes<br>
locally and complete the merge go for it.<br>
<span class="HOEnZb"><font color="#888888"><br>
Mark<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> On Mon, Dec 18, 2017 at 4:02 PM, S. Lockwood-Childs <<a href="mailto:sjl@vctlabs.com">sjl@vctlabs.com</a>> wrote:<br>
> > On Mon, Dec 18, 2017 at 03:17:25PM -0500, Derek Straka wrote:<br>
> > > I have several customers who have optimized for space and would like to<br>
> ><br>
> > see<br>
> ><br>
> > > the capability maintained unless core removes the ability to split<br>
> > > python<br>
> > > packages out. They also remove the *.py files in favor of *.pyo files<br>
> ><br>
> > (via<br>
> ><br>
> > > a custom packaging mechanism). I have automated tests that go through<br>
> ><br>
> > the<br>
> ><br>
> > > module importing on each of the meta-python packages to ensure it works<br>
> ><br>
> > on<br>
> ><br>
> > > minimal python installations. When other contributors don't do provide<br>
> > > that functionality, I either catch it when I do package update or when<br>
> > > it<br>
> > > breaks for one of my customers. I'm fine if you don't want to perform<br>
> ><br>
> > the<br>
> ><br>
> > > checks yourself and it breaks my use case with missing dependencies, but<br>
> ><br>
> > I<br>
> ><br>
> > > would prefer that you don't remove the dependencies that are currently<br>
> > > in<br>
> > > place. Thanks.<br>
> ><br>
> > Me too -- some of my projects still use NAND for rootfs, where space is<br>
> > tight and<br>
> > ability to split out python modules is very useful. Thus it is not an<br>
> > unused<br>
> > feature, though many projects have SD/eMMC for rootfs and those ones<br>
> > generally<br>
> > will not care about it.<br>
<br>
</div></div></blockquote></div><br></div>