> On Nov 1, 2016, at 9:33 AM, Alexander Kanavin > <alexander.kana...@linux.intel.com> wrote: > > On 11/01/2016 06:06 PM, Khem Raj wrote: > >>>> we should specify boost/boost/1.62.0/boost_1_62_0.tar.bz2 instead of >>>> boost/boost/boost_1_62_0.tar.bz2 >>> >>> Incorrect. That will still download a master snapshot tarball. Only if the >>> 'project/' is prefixed, SF will give you the release tarball. >> >> if we need projects/ then it should be encoded into SOURCEFORGE_MIRROR >> variable in bitbake.conf. Since that required for >> every sf.net project. > > Would you then also fix the remaining recipe-specific part of the URI in all > those recipes? I don't have the bandwidth for that right now, and it's a > problem that is unlikely to happen in other recipes. >
I wonder if same problem would not happen for other sf.net packages. probably we never run into it probably because it gets backed up on yp download mirror and then used. I am not expecting you to fix it, don't worry.
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
