Re: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
On 10/6/07, Adrian Aichner wrote:
> Vin Shelton writes:
> > I recently made a new gnuclient_setup window kit.
>
> Thanks Vin, it works great for me!
>
> I would like to make it easy from the XEmacs website to find and
> install your new gnuclient_setup window kit.
>
> I think about putting in a
> XEmacs Community News
> item for this.
>
> Furthermore I think that download links for gnuclient_setup.exe should
> go into http://www.xemacs.org/Download/win32/
Yes, I think it works well enough that we can move it out of the
testing directory.
Great!
> Vin, do you want to copy/mv
> http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
> over to
> http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
Sounds like you think we should "go public". I agree.
Good.
I had been thinking of waiting for the -b28 release. (Oops - I guess
I missed that triggering event :-) .) I don't see any particular
reason to wait for the impending -b29 release. I'll copy the file
over.
Thanks!
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
Here's what I'd suggest:
Remove contents of
http://ftp.xemacs.org/xemacs/binaries/win32/installshield/
http://ftp.xemacs.org/xemacs/binaries/win32/netinstall/
nhttp://ftp.xemacs.org/xemacs/windows/ReadMe-21.4.20
http://ftp.xemacs.org/xemacs/windows/XEmacs_Setup_21.4.20.exe
Copy (moving would require perfect timing relative to website update)
http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
Copy
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21.5-b...
Q: Is this really 21.5-b28 or CVS as of 2007-09-26?
Remove all content of
http://ftp.xemacs.org/xemacs/windows/testing
once the website changes have been committed.
Could you do that please?
> I think we never announced the beta binary kits for Windows.
>
> Should
> http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
> also be moved over, or should I link to the testing location from the website?
Well, I think you should link to the new location in the InnoSetup
directory and leave the windows/testing directory for the adventurous.
Do you mind making the changes to the website?
OK, I've started to make the required updates to
xemacs-builds\adrian\website\package-get-2-download-sites.el
and
xemacsweb\Download\win32\index.content
That doesn't mean I wouldn't love to see others to actively work on
the XEmacs website.
Anybody is welcome!
We'll need to coordinate the copying of files in the ftp site and the
commit of my website update.
Please let me know when the files are in place in the new locations.
>
> Perhaps it's time to remove the information about the outdated
> Netinstall
> and
> InstallShield
> kits from that page, and remove the kits from the ftp sites too?
>
> Any objections?
Well, they're pretty old (mostly circa 1999 - 2001). I don't think
keeping them around does the project any good.
Yep, I have worked that into my suggestions above.
> I am noting two regressions using gnuclientw vs. winclient (which I used
> before):
>
> When I sent a file to XEmacs for editing via winclient before, it
> would always raise the XEmacs frame.
>
> Now, when I do this, the file gets loaded in the running XEmacs OK,
> but the frame does not get raised.
>
> e.g. C-u in firefox (Firefox->View->Page Source)
Yes, I see this also. gnuclientw is supposed to handle this.
I thought gnuclientw only avoids the DOS prompt window to pop up.
Should it also raise the XEmacs frame?
>
> The other regression is that no new XEmacs is started when none is running.
>
> Instead I get the error message:
>
> ---------------------------
> c:\\Program Files\\XEmacs\\XEmacs-21.5-b28\\i586-pc-win32\\gnuclientw.exe
> ---------------------------
> Could not start runemacs
> ---------------------------
> OK
> ---------------------------
I'll investigate and see if I creating a runemacs.cmd file in the
gnuclientw directory suffices.
That would be great!
(BTW, I had to boost TRANSACTION_TIMEOUT to make winclient wait long
enough to start up XEmacs.)
Thanks for the testing and the feedback, Adrian!
Thanks for making gnuclient trivial to install for everybody
on Windows!
Adrian
- Vin
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta