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 had a need to run something on my Windows machine today which
required a newer version of Cygwin than the ancient one that was
installed there. After I upgraded to the current version (1.7.9) I
can't start a shell in XEmacs (via M-X shell) using Cygwin's version of
bash. When I try to do so I get
Process bash.exe exited abnormally with code 35584
3 [sig] bash 1168 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
1556 [sig] bash 1168 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
The stack dump is uninteresting except that the crash happens at offset
0x169220 in cygwin1.dll. It appears that this crash happens very early
on, before it's read /etc/profile. I see that I also have similar
stack dumps from other programs (find.exe and xargs.exe) in the XEmacs
directory all exactly the same.
I installed the latest Windows version of XEmacs from the installer at
<http://ftp.xemacs.org/pub/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21...>
and tried starting it with --vanilla. This didn't make any difference.
I also did a clean install of Cygwin 1.7.9 in case there was any crud
left around from the old version. This also didn't help. I'm running
on an old Dell with Windows XP Professional SP3. Perhaps that's the
problem. I probably should install Windows on my Mac under one of the
emulators, but that's more than I want to get into right now.
I've Googled around a bit and although others have seen this problem,
none of the solutions (mostly involving changing ownership of Cygwin
files and running rebaseall) did any good. The bash shell runs fine
when I start it using the .bat file installed by Cygwin, so it's
basically working, but it won't run in an XEmacs shell window.
Has anyone else seen this or know how to fix it? This little episode
reminds me why I avoid using Windows, but sometimes it's necessary.
Mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi!
I need to push the top-level ChangeLog in the package repository. This
fails due to cross-branch stuff. I suppose it would succeed if I could
push only this directory. Is this possible?
Thanks,
norbert.
--
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi, I compiled xemacs myself and installed into $HOME/xemacs-without-ipv6-cname
I then made a symlink of $HOME/xemacs-without-ipv6-cname/bin/xemacs to $HOME/bin/xemacs
I untarred the sumo tarball from http://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo-2009-02-17.tar.gz and untarred it into $HOME/xemacs-without-ipv6-cname/lib/xemacs, which made a directory called xemacs-packages there.
When I run xemacs, I am not able to update my packages.
I go to Tools -> Packages -> Set Download Site -> Official Releases -> US and choose US Main.
I then go "update package index" or any other command in the Tools menu about Packages and it complains: "symbol's value as variable is void: allow-remote-paths"
Can anyone help me with this? Thanks.
--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue, Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
Uwe Brauer writes:
> >> Regarding Re: subr.el (21.5.31) for 21.5.29; "Stephen J. Turnbull" <stephen(a)xemacs.org> adds:
> As far as I can see you submitted a C patch and when we
> talked about last time you found that patch too, hm
> aggressive. I strongly vote to apply it, since I
> have not found any problems so far,
No, *you* won't see any problems with it. The problems are entirely a
matter of style and clean internal APIs. I think it was Aidan (or
maybe Ben) who deliberately changed that particular API in a backward
incompatible way. I *know* that that implementation is going to
change radically in the future (it depends on Mule charsets, which
will eventually be reimplemented in terms of Unicode code point
blocks), so I really don't want to be bound to maintain any more
backward compatibility in that area than absolutely necessary.
> So that makes it your call :-)
OK, I'll work something up for x-symbol and get it committed.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi, XEmacs.
When I do "hg commit", I get the error message
abort: no username supplied (see "hg help config")
. hg help config gives a list of possible config files, and when I get
as far as 'man hgrc', my eyes start glazing over.
Would somebody please give me a quick tip on how to fix this error, and
possibly even warn me of other things to come.
Thanks!
--
Alan Mackenzie (Nuremberg, Germany).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Uwe Brauer writes:
> Maybe I did not compile 21.5.29 correctly:
I think this may be a long-standing bug in XEmacs Customize. You need
to specify --with-widgets=$TOOLKIT in order to get display of the
buttons that are implemented as native button widgets.
> but when I try to use customize-option, say the Set Save and Done
> button, which I see in 21.4.22 are not there, (the reset button is)
> and therefore I cannot make any changes.
As a workaround, you can still use the [State] "button":
> ,----
> | This is a customization buffer.
> | Type RET or click button2 on an active field to invoke its action.
> | Invoke [Help] for more information.
> |
> | Operate on everything in this buffer:
> | reset
> |
> | Reftex Include File Commands: *
> | [INS] [DEL] String: include
> | [INS] [DEL] String: input
> | [INS] [DEL] String: subfile
> | [INS]
> | [State]: this option has been set and saved.
A
|
right here
To invoke it you TAB to it then use RET to display an action menu.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-10-18 - 2011-10-25)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
533 open ( +0) / 274 closed ( +0) / 807 total ( +0)
Open issues with patches: 11
Average duration of open issues: 944 days.
Median duration of open issues: 993 days.
Open Issues Breakdown
new 210 ( +0)
deferred 6 ( +0)
napping 4 ( +0)
verified 54 ( +0)
assigned 150 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta