|
From: Per P. <per...@ma...> - 2004-10-21 17:08:20
|
On Oct 21, 2004, at 18:08, Ethan Merritt wrote: > On Thursday 21 October 2004 05:00 am, Per Persson wrote: >> Hi, >> I've cleaned up my distro script for Mac OS X and would like to add it >> and it's supporting files to CVS. >> >> I suppose the top dir rather than src/ is the appropriate location for >> a directory with the files? >> Any objections to naming that dir "MacOSXDistro"? > > I'm not objecting, at least not yet, but I'm curious exactly what files > these are. I managed to install gnuplot on OSX directly from the > existing > tree, and I am a total novice user to OSX. What is needed beyond > what is there already? I'm talking about a script and supporting files to create the binary installer and documentation in PDF that people right now are downloading from SF. Nobody is questioning your ability to type ./configure;make but some users prefer a double-clickable standard installer. In case I choose not to devote time to this project anymore, at least there would be a way to create an installer for Mac OS X from a point release by running a script. This was previously discussed: On Oct 2, 2004, at 13:15, Hans-Bernhard Broeker wrote: > >> In the long term, should I add the script (that creates installers) >> and >> a few (3 at the moment) supporting files to gnuplot or should I keep >> it >> separate? > > I think they should go into gnuplot. We already lost at least one > complete Macintosh port because its source never was integrated with > the mainline source. No good reason to let that happen again. Well, It might happen again. >> It relies on a GPL'd utility to pack stuff up. AINAL, but that should >> not AFAICT cause any license violations. Comments? > > The existing build chain uses many GPL utitilities (gmake, autoconf, > etc). This was in response to a question raise by HBB in a previous mail. /Per |