Menu
▾
▴
clisp-devel
|
From: Elliott S. <ell...@gm...> - 2007-11-02 05:52:04
|
I've been playing around with making an NSIS installer in preparation for writing a Windows installer for CLISP. I finished a small installer which installs a little GUI Hello World app written in CLISP by Frank Buss (http://www.frank-buss.de/lisp/clisp.html). It installs the exe as well as (optional) start menu and desktop shortcuts, and comes with an uninstaller. I am assuming I can't send attachments on this list, so I uploaded the installer to my website at http://blackthorncentral.net/files/test_install.zip . I would appreciate any feedback on how it works. Thanks. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Elliott S. <ell...@gm...> - 2007-11-03 02:06:36
|
I finished a basic Windows installer for CLISP. It does most everything the install.bat and install.lisp did in the standard binary distributions: it creates a start menu folder, desktop shortcut, gives the user control over the desired linked set, and sets up file associations. As a starting binary package, I used clisp-2.42-win32-with-readline-and-gettext.zip. There are some rough spots in the installer; for example the uninstaller deletes the entire installation directory even if the user added extra files after installation. It also deletes the start menu folder it gave the user the option of creating even if the user choose not to create that folder. (If the folder doesn't exist, it obvious doesn't delete anything. But it could potentially interfere with multiple installations.) The installer is only capable of English at the moment, although since I used almost all the default values for text, it should be possible to enable more languages without much trouble. It would be nice to have someone test the installer. I have uploaded it to my website; here is the url: http://blackthorncentral.net/files/clisp-2.42-win32-installer.zip . -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Jack U. <jd...@gm...> - 2007-11-03 02:54:09
|
On Nov 2, 2007 8:06 PM, Elliott Slaughter <ell...@gm...> wrote: > I finished a basic Windows installer for CLISP... Good job! > It would be nice to have someone test the installer. I have uploaded > it to my website; here is the url: > http://blackthorncentral.net/files/clisp-2.42-win32-installer.zip . A couple nits -- it installed the base linking set even though I left that option unchecked. Also, the uninstall did not remove the desktop shortcut that it created. I wonder if your installer should allow both the base and full linking sets to be installed side-by-side if the user wants, rather than only allowing one or the other to be selected? Otherwise, it worked fine here. Great work! -- Jack Unrue |
|
From: Elliott S. <ell...@gm...> - 2007-11-03 03:22:24
|
> It installed the base linking set even though > I left that option unchecked. The way the installer is set up right now, it just pulls in the files with one massive file glob, so the installer doesn't actually know the difference between the two linking sets. It just links all the shortcuts and file associations it creates to the chosen linking set. I did this firstly because it was just easier, and secondly because that's what you get when you install manually from the zip file and run install.bat. It wouldn't theoretically be that difficult to change... I just haven't tried yet. > I wonder if your installer should allow both the base and > full linking sets to be installed side-by-side if the user wants, > rather than only allowing one or the other to be selected? Again, same as above. However, if you wanted to have the installer remove the linking set that didn't get used, and allow the user to check both to install both, you would have to have two sets of options, one for what to install, and one for what to associate. And that might get a little difficult. Seeing as it only amounts to 8 MB, it probably isn't worth worrying about it. (If a user really had *that* little hard drive space they could delete the other linking set manually.) > Also, the uninstall did not remove the desktop shortcut that it created. Hmm... It works fine for me.... Which version of Windows are you on? Did you choose to install for just yourself, or all users? Would it be possible for you to export and send me the registry entries under HKEY_CLASSES_ROOT\GNU CLISP 2.42 when you have it installed? Also, could you or someone else experiment with using the installer with multiple users? In particular I am interested in what happens when one user attempts to uninstall the installation of another user. When I try it, the uninstaller says it completes, but if you look at the details of uninstallation, it hasn't actually done anything. I don't know if this is a feature of NSIS or a bug in my code... but at the very least I want to know if other people have the same results. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Elliott S. <ell...@gm...> - 2007-11-03 05:57:05
|
I added support for the PATH environment variable. Still have to get around to looking into linking sets (if it is decided to be worth the effort) and the persistent desktop shortcuts (I triple checked again, and it works for me...). Again the file can be downloaded at http://blackthorncentral.net/files/clisp-2.42-win32-installer.zip . I had a small issue with the license, because some of the names of developers were corrupted in the text file I recieved. Two names in particular had an odd look to them: "J=C3=BCrgen Weber" and "J=C3=B6rg H=C3=B6hle". I looked on clisp.cons.org, and found a "J=F6rg H=F6hle" who i= s probably the "J=C3=B6rg H=C3=B6hle" in the text file, but I couldn't find t= he other. On google I found a "J=FCrgen Weber" but I have absolutely no idea if this is the right person or not. If anyone who knows these names could inform me of the correct spellings, I would be happy to correct the license file. --=20 Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Jack U. <jd...@gm...> - 2007-11-03 20:09:23
|
On Nov 2, 2007 9:22 PM, Elliott Slaughter <ell...@gm...> wrote: > > > Also, the uninstall did not remove the desktop shortcut that it created. > > Hmm... It works fine for me.... Which version of Windows are you on? WinXP SP2 > Did you choose to install for just yourself, or all users? For myself only. I configure my account as a Limited User and run the installer as such. That might be a factor. > Would it be possible for you to export and send me the registry > entries under HKEY_CLASSES_ROOT\GNU CLISP 2.42 when you > have it installed? I don't see it under HKEY_CLASSES_ROOT. I did find it under HKEY_CURRENT_USER\.....\Start Menu2\Programs Uploaded here: http://lispwidgets.net/071103/clisp-hkey-current-user.reg -- Jack Unrue |
|
From: Arseny S. <am...@ic...> - 2007-11-03 07:18:16
|
Hi, Elliott, thanks for the installer! > The way the installer is set up right now, it just pulls in the files > with one massive file glob, so the installer doesn't actually know the > difference between the two linking sets. It just links all the > shortcuts and file associations it creates to the chosen linking set. > I did this firstly because it was just easier, and secondly because > that's what you get when you install manually from the zip file and > run install.bat. It wouldn't theoretically be that difficult to > change... I just haven't tried yet. >> I wonder if your installer should allow both the base and >> full linking sets to be installed side-by-side if the user wants, >> rather than only allowing one or the other to be selected? I seem to remember why two different linking sets are required. There are some system functions in the full linking set what are exist not on all systems. I.e. it were absent on windows 98. I even wrote some code to dynamically load some of them and if they're absent report runtime error at the time the function is invoked, so lisp.exe can be loaded. I wonder if the need in the two linking sets still present. So, if it is the only reason to have two lisp versions, you can leave the installer as is in this regard, because set the user working with is related to his operating system. But I see that now those functions are in both linking sets and the only difference I could find is the presence of PCRE package in the full one. Starting shortcut should be "Gnu Clisp x.xx", as it is for another programs, not "Run GNU Clisp". I could not find clisp record in the "Add/Remove programs" in the Control Panel. Probably the record should be placed there. Finally, novice user should be told somehow about the difference between the two linking sets. Actually, me too. -- Arseny |
|
From: Elliott S. <ell...@gm...> - 2007-11-03 18:40:53
|
On 11/3/07, Arseny Slobodyuk <am...@ic...> wrote: > Hi, Elliott, thanks for the installer! You're welcome. > Starting shortcut should be "Gnu Clisp x.xx", as it is for another > programs, not "Run GNU Clisp". Done. > I could not find clisp record in the "Add/Remove programs" in the > Control Panel. Probably the record should be placed there. Added registry values for Add/Remove Programs. I tested it on XP, but I would like someone to test it on Vista to make sure. > Finally, novice user should be told somehow about the difference > between the two linking sets. Actually, me too. Yeah, if someone could tell me the difference, I would be able to write a better description. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Jack U. <jd...@gm...> - 2007-11-03 20:30:31
|
On Nov 3, 2007 12:40 PM, Elliott Slaughter <ell...@gm...> wrote: > > Yeah, if someone could tell me the difference, I would be able to > write a better description. For general info, see http://clisp.cons.org/impnotes.html#modules The top-level INSTALL file in the clisp source tree describes what is nominally the base linkset: syscalls portable OS call interface i18n user program internationalization regexp POSIX regular expressions readline advances command line editing and history Whereas the "full" linkset can have additional modules. The INSTALL file describes these optional modules. -- Jack Unrue |
|
From: Elliott S. <ell...@gm...> - 2007-11-04 04:37:27
|
I found the error that was preventing the desktop shortcut from being uninstalled. Apparently Windows doesn't give limited users access to HKEY_LOCAL_MACHINE, so it wouldn't delete the shortcut. I fixed the problem by writing to HKEY_CURRENT_USER instead. Also, I managed to fix Add/Remove Programs so that it only shows CLISP to the user who installed it if installed for the current user, and for all users if installed for all users. However, users can't uninstall the installations of other users, even if they manually run the uninstaller themselves. This wasn't intentional (although it may not be a bad thing)... I don't know if this is an installer bug or a feature of NSIS, but either way I don't think I'll bother to change it. I added the list of modules installed to the descriptions of the base and full linking sets. (I got the list using clisp -K base|full --version, so it should be accurate for the package.) I would still like to know the names of "J=C3=BCrgen Weber" and "J=C3=B6rg H=C3=B6hle" if possible. The new installer is again available at http://blackthorncentral.net/files/clisp-2.42-win32-install.zip . And thanks again everyone for your support. --=20 Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Karsten P. <Kar...@gm...> - 2007-11-04 13:14:25
|
>I would still like to know the names of "Jürgen Weber" and "Jörg >Höhle" if possible. googling for "Jürgen Weber clisp" I found the following page http://www.ibiblio.org/pub/historic-linux/distributions/slackware/2.1/usr/doc/clisp/COPYRIGHT It says...Authors: Generic CLISP: Bruno Haible, Michael Stoll Atari version: Bruno Haible, Michael Stoll Amiga version: Bruno Haible, Jörg Höhle DOS version: Bruno Haible, Bernhard Degel, Jürgen Weber OS/2 version: Bruno Haible Unix version: Bruno Haible PCL: Richard Harris, ported by Bruno Haible Punimax: Bill Schelter, ported by Bruno Haible.So the right answer isJürgen Weber and Jörg Höhle. salu2Karsten |
|
From: Elliott S. <ell...@gm...> - 2007-11-04 17:38:16
|
Thanks. I correct the names in the license. I also managed to reduce the size of the installer by increasing the dictionary size from 8 MB to 16 MB. It is now less than half the size of the original binary package. Any further test would be appreciated. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Sam S. <sd...@gn...> - 2007-11-05 14:56:15
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > I would still like to know the names of "Jürgen Weber" and "Jörg > Höhle" if possible. please see file COPYRIGHT in the clisp distribution (source or binary). the file is utf-8, so you should be able to extract the correct spelling by opening it in a unicode-aware viewer. if woe32 does not support unicode, I think you can spell the names "Juergen Weber" and "Joerg Hoehle" (which is better than the horror that I see above). just in case: Jörg Höhle Jürgen Weber http://clisp.cvs.sourceforge.net/*checkout*/clisp/clisp/COPYRIGHT (ff: view -> character encoding -> unicode) Sam -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHLy8EPp1Qsf2qnMcRAjotAJ9wcBRB62IoUNReHqGI/17CMv0AugCeN+Lh 7LJGRkHOPyNUlHPoAn+rM38= =rz3i -----END PGP SIGNATURE----- |
|
From: Elliott S. <ell...@gm...> - 2007-11-05 20:03:13
|
> > I would still like to know the names of "J=C3=BCrgen Weber" and "J=C3= =B6rg > > H=C3=B6hle" if possible. > > please see file COPYRIGHT in the clisp distribution (source or binary). > the file is utf-8, so you should be able to extract the correct spelling > by opening it in a unicode-aware viewer. Yeah, thanks. I thought WordPad or at least OpenOffice would recognize the encoding automatically but I guess not. > if woe32 does not support unicode, I think you can spell the names > "Juergen Weber" and "Joerg Hoehle" (which is better than the horror that > I see above). > just in case: > J=F6rg H=F6hle > J=FCrgen Weber Yes, rtf supports unicode, so those characters are fine; I don't need the alternate spelling in this case. The installer has been corrected. --=20 Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Jack U. <jd...@gm...> - 2007-11-06 03:37:09
|
On Nov 4, 2007 10:38 AM, Elliott Slaughter <ell...@gm...> wrote: > > Any further test would be appreciated. Looks good here. It would be cool if your script file(s) could be added to the CVS repo. I guess it could go into the existing win32msvc directory even though it's not specific to Visual C++. I'd be willing to contribute a readme, if that helps. -- Jack Unrue |
|
From: Elliott S. <ell...@gm...> - 2007-11-06 06:16:35
|
On 11/5/07, Jack Unrue <jd...@gm...> wrote: > It would be cool if your script file(s) could be added to > the CVS repo. I guess it could go into the existing win32msvc > directory even though it's not specific to Visual C++. Yeah, that is probably the next step. I don't know much about CVS... I downloaded some Tortoise CVS because it seemed easy to use, but I don't really know how to upload files to the server. One thing about the way I have been implementing the scripts so far: all my installer script files are named "install_..." because I placed them directly in the same folder as the clisp files, so I would know which files to ignore when grabbing files to install. I don't know what the setup will be like once I upload it to the server... I guess since individual developers (probably me) will be building the installer, I can depend on them to move the files to right place before running them... although perhaps I should change my assumptions about how the build process will occur. (Either way, this probably needs to be documented... see below.) > I'd be willing to contribute a readme, if that helps. That might be helpful, as noted above. Also, since I am new to development, I am wondering on what level I get credit for working on this installer. I figure I can add my name to the source code of the installer script... but do I get copyright over the source of the script? I'm not sure what open source dictates with respect to this. Do I have any intellectual rights to my code? Or is this simply my contribution to the community, and this project (and thus its legal rights) now falls into the hands of everyone in the clisp project? Do I get to add a line with my to the copyright notice/license in the installer? Elsewhere? Thanks for answering my questions. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Hoehle, Joerg-C. <Joe...@t-...> - 2007-11-06 10:12:33
|
Elliot Slaughter wrote: >I would still like to know the names of "J=C3=BCrgen Weber" and = "J=C3=B6rg H=C3=B6hle" if possible. What do you want my name (J=F6rg H=F6hle) for? Please note that if you see the above horrors in your editor, you're in = serious danger of damaging source files if you save them after adding or = editing some Umlauts. The reason is that the file may afterwards contain Umlauts encoded as = UTF-8 and others as ISO-8859-1. In other words the format became = corrupted, and somebody will need to go through it by hand and fix it. So you really should tell your editor to open the file with the correct = encoding. Regards, J=F6rg H=F6hle. |
|
From: Elliott S. <ell...@gm...> - 2007-11-06 17:53:37
|
On 11/6/07, Hoehle, Joerg-Cyril <Joe...@t-...> wrote: > Elliot Slaughter wrote: > >I would still like to know the names of "J=C3=BCrgen Weber" and "J=C3=B6= rg > H=C3=B6hle" if possible. > What do you want my name (J=F6rg H=F6hle) for? The COPYRIGHT file is being used for the license shown in the installer, and the above unicode characters were not being shown properly. > Please note that if you see the above horrors in your editor, you're in s= erious danger of > damaging source files if you save them after adding or editing some Umlau= ts. > The reason is that the file may afterwards contain Umlauts encoded as UTF= -8 and others > as ISO-8859-1. In other words the format became corrupted, and somebody = will need to > go through it by hand and fix it. I did not modify any of the original files. I simply copied the COPYRIGHT file and made sure it would be viewed properly in the installer license. --=20 Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Sam S. <sd...@gn...> - 2007-11-06 15:29:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > On 11/5/07, Jack Unrue <jd...@gm...> wrote: >> It would be cool if your script file(s) could be added to >> the CVS repo. I guess it could go into the existing win32msvc >> directory even though it's not specific to Visual C++. > > Yeah, that is probably the next step. I don't know much about CVS... I > downloaded some Tortoise CVS because it seemed easy to use, but I > don't really know how to upload files to the server. you won't be able to - you need write access for that, and before I can grant you write access, you will have to get a sourceforge account. you will have write access to the directory where the install files will reside (win32msvc sounds fine). actually, I would like to review the files before they go into the CVS. Could you please make them available for download? > One thing about the way I have been implementing the scripts so far: > all my installer script files are named "install_..." because I placed > them directly in the same folder as the clisp files, so I would know > which files to ignore when grabbing files to install. I don't know > what the setup will be like once I upload it to the server... I guess > since individual developers (probably me) will be building the > installer, I can depend on them to move the files to right place > before running them... although perhaps I should change my assumptions > about how the build process will occur. (Either way, this probably > needs to be documented... see below.) you can copy them over from win32msvc to the build directory. >> I'd be willing to contribute a readme, if that helps. > > That might be helpful, as noted above. > > Also, since I am new to development, I am wondering on what level I > get credit for working on this installer. I figure I can add my name > to the source code of the installer script... but do I get copyright > over the source of the script? I'm not sure what open source dictates Your code remains copyrighted by you. You are releasing it under the GNU GPL v2 or later, at the user discretion. This means that the CLISP project can distribute your code with CLISP. IANAL. > Do I get to add a line with my to the copyright > notice/license in the installer? Elsewhere? I edit COPYRIGHT just to update the dates :-) Bruno, as the main author, gets to decide who is mentioned there and how. You do get a record in your name in the src/ChangeLog file (along with dozens other CLISP contributors). Thanks. Sam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMIhBPp1Qsf2qnMcRAkbCAJ9iMQW2MhPHgmQGLd7XWRANpGr+bgCgl1B1 0a4SxfubFCDgRxjPT1ShwAs= =abDh -----END PGP SIGNATURE----- |
|
From: Elliott S. <ell...@gm...> - 2007-11-06 18:34:39
|
On 11/6/07, Sam Steingold <sd...@gn...> wrote: > > > It would be cool if your script file(s) could be added to > > > the CVS repo. I guess it could go into the existing win32msvc > > > directory even though it's not specific to Visual C++. > > > > Yeah, that is probably the next step. I don't know much about CVS... I > > downloaded some Tortoise CVS because it seemed easy to use, but I > > don't really know how to upload files to the server. > > you won't be able to - you need write access for that, and before I can > grant you write access, you will have to get a sourceforge account. > you will have write access to the directory where the install files will > reside (win32msvc sounds fine). I already have a sourceforge account; my username is slaguth. > actually, I would like to review the files before they go into the CVS. > Could you please make them available for download? http://blackthorncentral.net/files/clisp-win32-install-source.tar.gz -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Sam S. <sd...@gn...> - 2007-11-06 19:20:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > >> actually, I would like to review the files before they go into the CVS. >> Could you please make them available for download? > > http://blackthorncentral.net/files/clisp-win32-install-source.tar.gz thanks. what is "nsh"? is it some sort of windows shell interpreter? are these two scripts run only during package creation or during installation too? can the nsh scripts be replaced with lisp scripts? Sam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHML5YPp1Qsf2qnMcRArZ6AJ4+UpxHQzpu/syaaZp/aS6dpvtI3wCcDMw0 cSASpZ8RxHawqAdTGDFF0Ao= =3KWp -----END PGP SIGNATURE----- |
|
From: Sam S. <sd...@gn...> - 2007-11-06 19:21:19
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > http://blackthorncentral.net/files/clisp-win32-install-source.tar.gz why is COPYRIGHT included as RTF and not plain text? it would be better to use plain text instead of maintaining two essentially identical files. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHML6iPp1Qsf2qnMcRAkfDAJ99aFOmeBV+Oav9PBFalxLOk9EoawCgnHw2 geyOp0O3h8Uxg3C5K47j57c= =5rQ2 -----END PGP SIGNATURE----- |
|
From: Elliott S. <ell...@gm...> - 2007-11-06 23:45:39
|
Sam Steingold <sd...@gn...> wrote: > what is "nsh"? is it some sort of windows shell interpreter? > are these two scripts run only during package creation or during > installation too? > can the nsh scripts be replaced with lisp scripts? The nsh files are NSIS header files, containing some code written by the NSIS community. They are linked at compile time, and are embedded in the installer. My only reason for moving them to files outside the main install script was just so they wouldn't clutter the script. While it would be possible to move some of the install functionality to external lisp scripts, as a part of the project, I tried to write all the necessary functionality into the installer, so you wouldn't have to depend on functionality from CLISP in the middle of its installation. Also, one of the header files (is_user_admin.nsh) definitely couldn't be moved to a lisp script, because it needs to execute before the installer displays the components page. > why is COPYRIGHT included as RTF and not plain text? > it would be better to use plain text instead of maintaining two > essentially identical files. Just the formatting of the text. If you use the text file directly, the installer doesn't recognize the unicode characters discussed earlier. Also, the font used by the installer is not a fixed width font, which makes all the spacing appear a little off, especially in sections with many lines padded by variable spacing. The other thing is the line "Hey Emacs! -*- coding: utf-8 -*-", presumable necessary for emacs to recognize the UTF-8 characters, but which isn't helpful in the installer and doesn't particularly look good. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert |
|
From: Sam S. <sd...@gn...> - 2007-11-06 23:56:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elliott Slaughter wrote: > Sam Steingold <sd...@gn...> wrote: >> what is "nsh"? is it some sort of windows shell interpreter? >> are these two scripts run only during package creation or during >> installation too? >> can the nsh scripts be replaced with lisp scripts? > > The nsh files are NSIS header files, containing some code written by > the NSIS community. They are linked at compile time, and are embedded > in the installer. My only reason for moving them to files outside the > main install script was just so they wouldn't clutter the script. OK, thanks. so what's missing is the src/makemake.in patch that would create the installer. >> why is COPYRIGHT included as RTF and not plain text? >> it would be better to use plain text instead of maintaining two >> essentially identical files. > > Just the formatting of the text. If you use the text file directly, > the installer doesn't recognize the unicode characters discussed > earlier. Also, the font used by the installer is not a fixed width > font, which makes all the spacing appear a little off, especially in > sections with many lines padded by variable spacing. The other thing > is the line "Hey Emacs! -*- coding: utf-8 -*-", presumable necessary > for emacs to recognize the UTF-8 characters, but which isn't helpful > in the installer and doesn't particularly look good. we need to find a way to generate this rtf automatically. this file is far to important for us to risk having two copies diverge... Sam. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMP84Pp1Qsf2qnMcRAuxuAJ4/8lDlJN2WNXUbIZPKULaZPHn/mQCcClJw +sc2XQBkmWvZMh5CT0iy4Oc= =R8nj -----END PGP SIGNATURE----- |
|
From: Elliott S. <ell...@gm...> - 2007-11-07 00:24:13
|
On Nov 6, 2007 3:56 PM, Sam Steingold <sd...@gn...> wrote:
> so what's missing is the src/makemake.in patch that would create the
> installer.
Not at all sure how to do that... And we still need to upload the
install files to the CVS, unless you did it without telling me. (BTW,
did you give me write access to the installer subdirectory of the CVS
repo?)
Also, my installer scripts currently assume they are running from the
same directory that houses clisp. If you want to be able to
automatically build them from win32msvc, then I'll need to make some
changes.
> we need to find a way to generate this rtf automatically.
> this file is far to important for us to risk having two copies diverge...
Agreed. But I'm not really sure how to do that. RTF is a human
readable format, so it is at least theoretically possible. If you
didn't mind the uneven lines, it would probably be possible to fix the
other problems without too much trouble... just add a little rtf
header, replace all new lines with the appropriate code ("\par"?),
remove the emacs encoding line, and fix the unicode in names.
--
Elliott Slaughter
"Any road followed precisely to its end leads precisely nowhere." -
Frank Herbert
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X