id summary reporter owner description type status priority milestone component resolution keywords cc parents 1095 Smarter extlib installs Christopher Allan Webber "Unfortunately, we have a last minute yak to shave for 0.8.0: if we want to fix #918, we should do it right, and that means no more committing (often minified or otherwise compiled) javascript libraries into our git tree. But how to do that? System packagers can take advantage of other system packages of javascript and the like (though admittedly we might not make this easy at present). In the meanwhile, if we want to make development easy for contributors and *not* have them battle about 5 language-specific package managers that may or may not cover all our needs to fill out extlib, it would be nice if there was a way to just script out ""fetch all this stuff and unpack it here"" I've been trying to model out what the data needs of such a file would look like, and this looks maybe about right-ish: {{{ EXTLIBS = [ Extlib( ""lato"", verify=check_md5(""ab516ef108""), install=fetch_and_unpack( ""http://example.org/lato-1.7.tar.gz"", move_from=""lato-1.7""), # complete and corresponding source c_and_cs=fetch_and_unpack(""http://example.org/lato-source.git"") ), Extlib( ""pdf.js"", verify=check_md5(""adc95ed383ec00cf4342bf4dd343e9bb""), install=fetch_and_unpack( ""http://example.org/pdf.js-8.7.tar.gz"", move_from=""pdfjs-8.7""), # complete and corresponding source c_and_cs=print_instructions(""git clone git://gitpit.example/pdfjs/"") ) ] }}} A script would still have to be written and carried alongside it. It might be nice to give it a more lax license than the rest of our code but I am somewhat loose about that." defect closed major 0.8.0 programming fixed