Hi,
Here comes yet another status report from the project of converting to
GPLv3 or later.
There are two lists of files below. The first list contains all files
that are in an undecided state. Please inspect: Do we need to do anything
with them. If so what?
The second list contains all files that we can leave untouched and the
reason for that. Please inspect: Are all reasons OK and correct?
Are we getting close to the were an inspection of the xemacs-gplv3
repository could be performed? With the intent that it that is OK we
could merge back to trunk and go GPLv3 or later?
----------------------------------------------------------------------
"CHANGES-beta"
"ChangeLog"
"PROBLEMS"
"README"
"README.GPLv3"
"etc/ChangeLog"
"etc/Emacs.ad"
"etc/InstallGuide"
"etc/NEWS"
"etc/ONEWS"
"etc/OONEWS"
"etc/README"
"etc/editclient.sh"
"etc/emacskeys.sco"
"etc/emacsstrs.sco"
"etc/gtkrc"
"etc/package-index.LATEST.gpg"
"etc/sample.Xresources"
"etc/xemacs.1"
"lib-src/ChangeLog"
"lib-src/README"
"lisp/ChangeLog"
"lisp/README"
"lisp/mule/mule-locale.txt"
"man/ChangeLog"
"man/README"
"modules/ChangeLog"
"modules/base64/Makefile"
"modules/common/configure-post.ac"
"modules/common/configure-pre.ac"
"modules/zlib/Makefile"
"nt/ChangeLog"
"nt/Emacs.ad.h"
"nt/Installation.el"
"nt/README"
"nt/Win32.cf"
"nt/lisp.ico"
"nt/site.def"
"nt/xemacs.dsp"
"nt/xemacs.dsw"
"src/ChangeLog"
"src/README"
"src/README.kkcc"
"src/m/README"
"src/s/README"
"src/s/freebsd.h"
"src/s/irix6-0.h"
"src/s/netbsd.h"
"src/s/sol2.h"
"tests/ChangeLog"
"tests/Dnd/README"
"tests/automated/README"
"version.sh.in"
----------------------------------------------------------------------
These files below are the files that we might be able to leave as
they are. The reason for why they need not to be changed is listed
after each file: (Some reasons are taken verbatim from private
communication or the "GPL version 3 source survey")
----------------------------------------------------------------------
"INSTALL" -> old FSF Documentation license
"config.guess" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"config.sub" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"etc/ETAGS.ChangeLog" -> BSD and GPL v2 or later
"etc/VEGETABLES" -> Not copyrightable.
"etc/XKeysymDB" -> MIT
"etc/ctags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/custom/example-themes/ex-custom-file" -> Generated(!?) or GPL V2 or later?
"etc/etags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/gnuattach.1" -> simple man link to gnuserv.1
"etc/gnuclient.1" -> simple man link to gnuserv.1
"etc/gnudoit.1" -> simple man link to gnuserv.1
"etc/refcard.ps.gz" -> Generated from refcard..tex
"etc/sample.Xdefaults" -> It is deprecated, so it can be removed but is only a three line reference to .Xresources
"etc/xemacs-X.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"info/dir" -> Generated(?)
"install-sh" -> MIT-style "no advertising" license
"lib-src/b2m.c" -> This is the version from GNU Emacs, so should be OK.
"lib-src/config.values.in" -> Generated.
"lib-src/emacs.csh" -> I don't think this even works with XEmacs ("emacsclient"), so I believe we can just delete it.
"lib-src/insert-data-in-exec.c" -> Compatible license.
"lib-src/mmencode.c" -> Compatible license.
"lisp/dump-paths.el" -> Empty file. Not copyrightable.
"lisp/term/bobcat.el" -> Emacs version has no explicit license declaration
"lisp/term/vt102.el" -> Emacs version has no explicit license declaration
"lisp/term/vt125.el" -> Emacs version has no explicit license declaration
"lisp/term/vt200.el" -> Emacs version has no explicit license declaration
"lisp/term/vt201.el" -> Emacs version has no explicit license declaration
"lisp/term/vt220.el" -> Emacs version has no explicit license declaration
"lisp/term/vt240.el" -> Emacs version has no explicit license declaration
"lisp/term/vt300.el" -> Emacs version has no explicit license declaration
"lisp/term/vt320.el" -> Emacs version has no explicit license declaration
"lisp/term/vt400.el" -> Emacs version has no explicit license declaration
"lisp/term/vt420.el" -> Emacs version has no explicit license declaration
"lock/.precious" -> Not copyrightable.
"modules/canna/install-sh" -> MIT
"modules/ldap/install-sh" -> MIT
"modules/postgresql/install-sh" -> MIT
"modules/sample/external/install-sh" -> MIT
"modules/sample/internal/install-sh" -> MIT
"move-if-change" -> Identical to GPLv3 or later Emacs version
"nt/Xmd.patch" -> GPLv2 or later but only a few lines
"nt/file.ico" -> MIT
"nt/minitar.c" -> Public domain
"nt/paths.h" -> Generated
"nt/xemacs.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"src/alloca.c" -> Public domain.
"src/depend" -> Generated
"src/emacs-marshals.c" -> Generated.
"src/emacs-widget-accessors.c" -> Generated.
"src/intl-auto-encap-win32.c" -> Generated.
"src/intl-auto-encap-win32.h" -> Generated.
"src/libsst.c" -> Compatible license.
"src/libsst.h" -> Compatible license.
"src/libst.h" -> Compatible copyright.
"src/linuxplay.c" -> Compatible license. (MIT-like)
"src/miscplay.c" -> Compatible license. (MIT-like)
"src/miscplay.h" -> Compatible license. (MIT-like)
"src/nas.c" -> Compatible license. (MIT-like)
"src/paths.h.in" -> Generated.
"src/s/openbsd.h" -> Too short. (< 10 lines)
"src/s/usg5-4-2.h" -> Too short. (< 10 lines)
"src/sunplay.c" -> Compatible copyright.
"tests/gtk/UNIMPLEMENTED" -> Does notes need a license?
"tests/tooltalk/beeps.el" -> Too short. (< 10 lines)
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I've been working on TLS support for a little while, and now have what
seems to be working nss, openssl, and gnutls lstream implementations.
The next challenge is making those available via the Emacs interface,
since that is what consuming packages expect. I thought I'd give you
a snapshot of what I've done so far (attached), just in case I get
abducted by aliens who need some operating system work done.
If you see anything that seems wrong or wrong-headed, let me know.
It's still early enough to change direction if I'm doing something
gratuitously stupid.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
New machine, trying 64-bit cygwin, but no joy so far in compiling from
latest sources.
Too soon to say if I've just not got my environment right yet - so at
this point just checking -- has anyone made this work yet?
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht(a)inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi all,
The Fedora project is attempting to move from 32x32 or smaller icons up to
at least 64x64, and preferably 256x256. They say that today's
high-pixel-density displays make the old icons look either (a) really tiny
or (b) fuzzy. Does anybody have, or have the capability to produce, a good
looking XEmacs icon at 64x64 or (better) 256x256? Thank you.
Non-artistically yours,
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
When I closed xemacs in my last session I had a file open in a directory
which does not exist anymore, however I now obtain on start up
the directory foo does not exist, Create?
And independent what I answer next time I start this message still pops
up, this is annoying, which package could cause such a behaviour?
Thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
We have had this problem for a long time in the buildbot. Two builds
on mac and one build on linux seems to be affected by it. Anyone who
can have a look at this?
Since its g++ involved, and the error message talks about not a
throw-expression(!), this sounds quite interesting. Don't you think?
Feel free to beat me to it! ;-)
----------------------------------------------------------------------
...
cd ./src && make all
g++ -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Weffc++ -g -O3 -fno-strict-aliasing -I/opt/local/include -Demacs -I. -I/Users/buildbot/builds/build-xemacs/rtoy_imac_osx_cfg1/build/src -DHAVE_CONFIG_H -I/usr/X11R6/include/freetype2 -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include -I/usr/X11/include abbrev.c
abbrev.c: In function 'Lisp_Symbol* abbrev_oblookup(buffer*, Lisp_Object)':
abbrev.c:234: error: '0' has type 'void' and is not a throw-expression
make[1]: *** [abbrev.o] Error 1
make: *** [src] Error 2
program finished with exit code 2
----------------------------------------------------------------------
Same problem but on linux so another error message.
----------------------------------------------------------------------
...
g++ -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Weffc++ -g -fno-strict-aliasing -Demacs -I. -I/home/buildbot/slaves/bot1name/matsl_cfg3/build/src -DHAVE_CONFIG_H -I/usr/include/freetype2 abbrev.c
abbrev.c: In function 'Lisp_Symbol* abbrev_oblookup(buffer*, Lisp_Object)':
abbrev.c:234:14: error: third operand to the conditional operator is of type 'void', but the second operand is neither a throw-expression nor of type 'void'
GNUmakefile:102: recipe for target 'abbrev.o' failed
make[2]: Leaving directory '/home/buildbot/slaves/bot1name/matsl_cfg3/build/src'
make[2]: *** [abbrev.o] Error 1
GNUmakefile:98: recipe for target 'src' failed
make[1]: Leaving directory '/home/buildbot/slaves/bot1name/matsl_cfg3/build'
make[1]: *** [src] Error 2
program finished with exit code 2
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
again a message of mine has not appeared in the list. I smime-signed
them, is this a problem?
I will resend that message via gmane.
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
On Fri, Oct 31, 2014 at 4:54 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> There is an error downloading. It seems to be permission issue. Please take a look.
Yes. That was just to see if anyone was paying attention. :-)
I have fixed the permissions.
Good luck!
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi, Biswajit -
I am copying the xemacs-beta list because your question might be of
general interest.
On Wed, Oct 29, 2014 at 11:13 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> I see that innosetup kits for 21.5.32 and later are not available on xemacs.org .
>
> The build instructions seem to be either not up-to-date or wrong for 21.5.32 and later. I tried with visual studio, but one after another problem kept cropping up in compilation.
>
> Would it be possible to provide innosetup binaries for the later beta releases ?
I do not currently have access to a Windows machine I can use to build
the setup kits. I do not currently have any plans to do this, I might
be able to resurrect an old XP VM I have lying around, but I probably
won't have enough free time to investigate this until Christmas.
Perhaps someone else on the xemacs-beta list would be interested in
picking up this work.
The build instructions are certainly finicky. They worked for me when
last I used them, but I will point out that they specify VS6, which is
more than a decade old by now.
Regards,
Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
Using Xemacs-21.5.33 mule I just found out,to my surprise, that I cannot
incremental search the symbol ” with the usual C-s C-w combination I
usually use. Is this a bug?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta