> Of course, either location will work fine with wget or curl, but this > is not about automation and build systems. This is about someone using > a graphical web browser, downloading the script, and following some > directions. The wiki inserts this HTTP header, which makes the browser > download instead of display it: > > Content-disposition: inline;filename=build-melt.sh > > But I guess this is a minor point. If the user cannot figure out how > to use Save As... or click Back and then right-click to download, then > they should not be attempting to use this build script.
I would tend to agree. A user can figure out how to "save as". Otherwise, I wouldn't mind synchronizing the files with the Wiki manually. They shouldn't change that often. > I am OK to use github since you plan to add other scripts for the build > server. > https://github.com/pez4brian/build-melt Just so I understand... Are you suggesting we keep all the scripts on github in my personal repository? It would work fine, but it seems a little arbitrary. I thought you could just create another repository at mltframework.org. Otherwise, we can create an mlt organization on github and keep the repo there. Either of those would make the most sense to me. > as for v2 vs. v3 of build-melt.sh, I will take care of that in my fork > and send you a pull request. It fixes some things on OS X for the > nearly ready build agent. I resolved your comments in this commit: https://github.com/pez4brian/build-melt/commit/76cd4de9513947b84ec17de0b035881ad6f96477 ~BM ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
