<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Ben,<div dir="ltr"><br>On Dec 22, 2018, at 5:09 AM, Ben Coman <<a href="mailto:btc@openinworld.com">btc@openinworld.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span></span></div></blockquote><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>It funny when the system seems to fight back.</div><div>Just as I think I resolve my freetype build issues, </div>my Windows build started failing as follows...<br>> wget -q --no-check-certificate -O ../../.thirdparty-cache/libpng-1.6.29.tar.gz <a href="ftp://ftp.simplesystems.org/pub/libpng/png/src/libpng16/libpng-1.6.29.tar.gz">ftp://ftp.simplesystems.org/pub/libpng/png/src/libpng16/libpng-1.6.29.tar.gz</a><br>> make: *** [../third-party/Makefile.libpng:19: ../../.thirdparty-cache/libpng-1.6.29.tar.gz] Error 8<br><br>What I see at <a href="ftp://ftp.simplesystems.org/pub/libpng/png/src/libpng16/">ftp://ftp.simplesystems.org/pub/libpng/png/src/libpng16/</a><br>is...<br><font face="monospace, monospace">Name Size Date Modified<br>libpng-1.6.34-LICENSE.txt 4.9 kB 29/09/2017, 08:00:00<br>libpng-1.6.34-README.txt 96 3B 29/09/2017, 08:00:00<br>libpng-1.6.34.tar.gz 1.4 MB 29/09/2017, 08:00:00<br>libpng-1.6.34.tar.gz.asc 819 B 29/09/2017, 08:00:00<br>libpng-1.6.34.tar.xz 975 kB 29/09/2017, 08:00:00<br>libpng-1.6.34.tar.xz.asc 819 B 29/09/2017, 08:00:00<br>lpng1634.7z 734 kB 29/09/2017, 08:00:00<br>lpng1634.7z.asc 819 B 29/09/2017, 08:00:00<br>lpng1634.zip 1.3 MB 29/09/2017, 08:00:00<br>lpng1634.zip.asc 819 B 29/09/2017, 08:00:00</font><div><br></div><div>So did version 1.6.29 exist yesterday but not today? </div><div>or am I going crazy?</div></div></div></blockquote><div><br></div>:-(<div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Anyway, should our builds avoid referencing external resources not under our control? Or would it be be better to copy the required tar files to a server our community controls, (either <a href="http://files.opensmalltalk.org">files.opensmalltalk.org</a> or <a href="http://file.pharo.org">file.pharo.org</a>)?</div></div></div></blockquote><div><br></div>I don’t see how the former is possible :-(. Do some variation of the latter is necessary. I like your suggestion of <a href="http://files.pharo.org">files.pharo.org</a>; <a href="http://files.opensmalltalk.org">files.opensmalltalk.org</a> doesn’t exist and do would need funding. I think adding the tar files to opensmalltalk-vm itself would be a huge mistake; it would cause the repository to bloat quite quickly right? So what are the logistics of using <a href="http://files.pharo.org">files.pharo.org</a>?</div><div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Plus btw our makefiles should verify sha1 checksums of these downloaded files via a field in the third-party/*spec files.</div></div></div></blockquote><div><br></div>+1</div><div><br><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>cheers -ben</div></div>
</div></blockquote></div></body></html>