GPLv3|L8R -- Status report - ready for inspection?
7 years, 6 months
Mats Lidell
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
Re: Loading startup changes load-path?
10 years, 8 months
Michael Sperber
Mats Lidell <matsl(a)xemacs.org> writes:
>>>>>> Michael Sperber <sperber(a)deinprogramm.de> writes:
>
>> It is intentional, to some degree: A long time ago, people screamed
>> bloody murder at me when the startup paths didn't give configure'd
>> paths precedence over those determined at run time. startup.el is just
>> the first file that knows about those paths. So there's no good
>> solution here that will make everybody happy, I'm afraid.
>
> But this happens while building the dump. What ever happens when you
> start your xemacs is another thing I think. Couldn't this behavior be
> controlled some how so that when building the dump we don't do this?
It could be done. My point is that, at least once upon a time, there
were people who didn't do it to be the way you want it to be. They do
have a point in that the already complicated behavior gets more
complicated when it's different at dump time.
--
Regards,
Mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
el-rcfiles v1.0
11 years
Didier Verna
Hello,
I've been using this for years, but never got to make it public until
recently. It's a very small and simple library for providing Unix-like
rc files to Emacs Lisp libraries.
All the details are here:
http://www.lrde.epita.fr/~didier/software/elisp/#el-rcfiles
and this is the commentary section, for quick reference:
;;; Commentary:
;; The purpose of el-rcfiles is to provide the equivalent of traditional
;; Unix rc files (i.e. configuration files) for Emacs Lisp
;; libraries. The advantages of using configuration files are the
;; following:
;; - your initialization file is less bloated,
;; - since configuration files are lazily loaded, your Emacs session
;; is (or begins) lighter. That is unless you already use lots of
;; EVAL-AFTER-LOAD forms...
;; Usage:
;; 1. Load the library, go to the rcfiles Custom group and tweak (or not).
;; 2. Put a call to (rcfiles-register-rc-files) in your initialization
;; file. This function can also be called interactively anytime you
;; add, remove or modify a configuration file.
;; 3. Put your configuration code for a library `foo' in a file called
;; `<rcfiles-directory>/foo<rcfiles-pseudo-extension>.el'.
--
Resistance is futile. You will be jazzimilated.
Scientific site: http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Texinfo 5.x and the packages
11 years, 1 month
Jerry James
Fedora updated its texinfo to version 5.0, and then version 5.1, in
the not-so-distant past. The XEmacs package and the XEmacs packages
packages [1] promptly stopped building, due to errors thrown by
texinfo while processing our texinfo sources. The attached patch is
an emergency patch that I threw together for our packages, just to get
things building for Fedora again. I don't think it is entirely
correct. Package maintainers, if there is a part in here for one of
your packages, and it looks correct to you, please pull that part out
and commit it. If it doesn't look correct, please suggest how to fix
it. Thanks,
Footnotes:
[1] Don't you just love overloaded terms?
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Latest 21.5 updates: texinfo breaks in compiling
11 years, 5 months
Robert Royar
As of "XEmacs 21.5 (beta33) \"horseradish\" 2257ac0e8a47+ [Lucid]
(x86_64-apple-darwin12.4.0, Mule) of Sat Jun 22 2013 on
grendel.frinabulax.org" the file man/texinfo.texi will not compile on Mac
OS X (10.8) using the system's makeinfo (version 4.8). I have macports
installed, and it supplies the 4.13 tech info package; however,
/opt/local/bin is usually after /usr/bin in my build environment. I suggest
that configure be given additional rules to assure that the supplied
makeinfo is new enough to compile the manual sources. When I run the
configure/build process with a path that places /opt/local/bin before
/usr/bin, the build and subsequent install succeed.
After 'make real clean', grabbing the changes with hg, configuring, and
issuing 'make' I get an error when makeinfo 4.8 is used. The error occurs
near the end of the build during the documentation compilation phase:
cd /Users/royar/src/xemacs-hg/man && make info
makeinfo -P texinfo -o ../info/texinfo.info texinfo/texinfo.texi
texinfo/texinfo.texi:10389: Unknown command `frenchspacing'.
texinfo/texinfo.texi:10392: Unknown command `frenchspacing'.
texinfo/texinfo.texi:10718: Unknown command `quotedblleft'.
texinfo/texinfo.texi:10718: Misplaced {.
texinfo/texinfo.texi:10718: Misplaced }.
texinfo/texinfo.texi:10719: Unknown command `quotedblright'.
texinfo/texinfo.texi:10719: Misplaced {.
texinfo/texinfo.texi:10719: Misplaced }.
texinfo/texinfo.texi:10720: Unknown command `quoteleft'.
texinfo/texinfo.texi:10720: Misplaced {.
texinfo/texinfo.texi:10720: Misplaced }.
texinfo/texinfo.texi:10721: Unknown command `quoteright'.
texinfo/texinfo.texi:10721: Misplaced {.
texinfo/texinfo.texi:10721: Misplaced }.
texinfo/texinfo.texi:10722: Unknown command `quotedblbase'.
texinfo/texinfo.texi:10722: Misplaced {.
texinfo/texinfo.texi:10722: Misplaced }.
texinfo/texinfo.texi:10723: Unknown command `quotesinglbase'.
texinfo/texinfo.texi:10723: Misplaced {.
texinfo/texinfo.texi:10723: Misplaced }.
texinfo/texinfo.texi:10724: Unknown command `guillemetleft'.
texinfo/texinfo.texi:10724: Misplaced {.
texinfo/texinfo.texi:10724: Misplaced }.
texinfo/texinfo.texi:10725: Unknown command `guillemetright'.
texinfo/texinfo.texi:10725: Misplaced {.
texinfo/texinfo.texi:10725: Misplaced }.
texinfo/texinfo.texi:10726: Unknown command `guilsinglleft'.
texinfo/texinfo.texi:10726: Misplaced {.
texinfo/texinfo.texi:10726: Misplaced }.
texinfo/texinfo.texi:10727: Unknown command `guilsinglright'.
texinfo/texinfo.texi:10727: Misplaced {.
texinfo/texinfo.texi:10727: Misplaced }.
texinfo/texinfo.texi:10925: Unknown command `textdegree'.
texinfo/texinfo.texi:10925: Misplaced {.
texinfo/texinfo.texi:10925: Misplaced }.
texinfo/texinfo.texi:10928: Unknown command `textdegree'.
texinfo/texinfo.texi:10928: Misplaced {.
texinfo/texinfo.texi:10928: Misplaced }.
texinfo/texinfo.texi:10968: Unknown command `geq'.
texinfo/texinfo.texi:10968: Misplaced {.
texinfo/texinfo.texi:10968: Misplaced }.
texinfo/texinfo.texi:10968: Unknown command `leq'.
texinfo/texinfo.texi:10968: Misplaced {.
texinfo/texinfo.texi:10968: Misplaced }.
texinfo/texinfo.texi:10972: Unknown command `geq'.
texinfo/texinfo.texi:10972: Misplaced {.
texinfo/texinfo.texi:10972: Misplaced }.
texinfo/texinfo.texi:10973: Unknown command `leq'.
texinfo/texinfo.texi:10973: Misplaced {.
texinfo/texinfo.texi:10973: Misplaced }.
texinfo/texinfo.texi:11082: Unknown command `clicksequence'.
texinfo/texinfo.texi:11082: Misplaced {.
texinfo/texinfo.texi:11082: Unknown command `click'.
texinfo/texinfo.texi:11082: Misplaced {.
texinfo/texinfo.texi:11082: Misplaced }.
texinfo/texinfo.texi:11082: Misplaced }.
texinfo/texinfo.texi:11108: Unknown command `clickstyle'.
texinfo/texinfo.texi:11108: ＠result expected braces.
texinfo/texinfo.texi:11109: Unknown command `clicksequence'.
texinfo/texinfo.texi:11109: Misplaced {.
texinfo/texinfo.texi:11109: Unknown command `click'.
texinfo/texinfo.texi:11109: Misplaced {.
texinfo/texinfo.texi:11109: Misplaced }.
texinfo/texinfo.texi:11109: Misplaced }.
texinfo/texinfo.texi:11108: ＠result missing close brace.
texinfo/texinfo.texi:17472: Unknown command `arrow'.
texinfo/texinfo.texi:17472: Misplaced {.
texinfo/texinfo.texi:17472: Misplaced }.
texinfo/texinfo.texi:17901: Unknown command `geq'.
texinfo/texinfo.texi:17901: Misplaced {.
texinfo/texinfo.texi:17901: Misplaced }.
texinfo/texinfo.texi:18051: Unknown command `leq'.
texinfo/texinfo.texi:18051: Misplaced {.
texinfo/texinfo.texi:18051: Misplaced }.
texinfo/texinfo.texi:10715: Unknown command `guilsinglright'.
texinfo/texinfo.texi:10715: Misplaced {.
texinfo/texinfo.texi:10715: Misplaced }.
texinfo/texinfo.texi:10713: Unknown command `guilsinglleft'.
texinfo/texinfo.texi:10713: Misplaced {.
texinfo/texinfo.texi:10713: Misplaced }.
texinfo/texinfo.texi:10711: Unknown command `guillemetright'.
texinfo/texinfo.texi:10711: Misplaced {.
texinfo/texinfo.texi:10711: Misplaced }.
texinfo/texinfo.texi:10708: Unknown command `guillemetleft'.
texinfo/texinfo.texi:10708: Misplaced {.
texinfo/texinfo.texi:10708: Misplaced }.
texinfo/texinfo.texi:10688: Unknown command `quotesinglbase'.
texinfo/texinfo.texi:10688: Misplaced {.
texinfo/texinfo.texi:10688: Misplaced }.
texinfo/texinfo.texi:10686: Unknown command `quotedblbase'.
texinfo/texinfo.texi:10686: Misplaced {.
texinfo/texinfo.texi:10686: Misplaced }.
makeinfo: Removing output file `../info/texinfo.info' due to errors; use
--force to preserve.
make[1]: *** [../info/texinfo.info] Error 1
make: *** [info] Error 2
--
Robert Royar <xemacs(a)royar.org>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
make-repeat-command/toggle functions
11 years, 5 months
Uwe Brauer
Hello
Years ago the following code was posted to Xemacs
;; by Adrian Kubala Adrian Kubala <adrian(a)sixfingeredman.net>
(defun make-repeat-command (symbol command-list)
"Command changes with each repetition.
SYMBOL is a symbol unique to this command."
(if (eq last-command symbol)
(set symbol (+ (eval symbol) 1))
(set symbol 0))
(if (>= (eval symbol) (length command-list))
(set symbol 0))
(call-interactively (nth (eval symbol) command-list))
(setq this-command symbol))
I find it extremely useful since it allows me to toggle functions and
bind them on one key like in
(defun my-home ()
(interactive "_")
(make-repeat-command 'my-home '(beginning-of-line-text
beginning-of-line
beginning-of-buffer)))
I asked the author whether he would mind if the code is included in
xemacs. But maybe meanwhile we have some similar functionality?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
gpg+gnus mua+ problems with create-image
11 years, 5 months
Uwe Brauer
Hello
I have used years ago succesfully gpg with gnus, I then switched to
smime without much problems.
Now under Xemacs 21.5.32 (33) mua gnus I cannot open any gpg encrypted
message (either inline or pgpmime), always pops up an error concerning
missing function create-image.
Since people on this list use gpg and gnus:
Have they every faced this problem?
thanks
Uwe Brauer
Debugger entered--Lisp error: (void-function create-image)
create-image(" redirect.\n" nil t)
mml2015-epg-key-image("AD24CFB593B61FDD")
mml2015-epg-key-image-to-string("AD24CFB593B61FDD")
mml2015-epg-signature-to-string((epg-signature . [good "AD24CFB593B61FDD" ultimate "5462A967D4B8761A7282AB35815DA2DC" (20941 . 58409) nil 1 2 1 3 nil]))
mapconcat(mml2015-epg-signature-to-string "\n" ((epg-signature . [good "AD24CFB593B61FDD" ultimate "5462A967D4B8761A7282AB35815DA2DC" ... nil 1 2 1 3 nil])))
mml2015-epg-verify-result-to-string(((epg-signature . [good "AD24CFB593B61FDD" ultimate "5462A967D4B8761A7282AB35815DA2DC" ... nil 1 2 1 3 nil])))
byte-code("..." [mm-security-handle context handles parameter value handle t nil mm-find-part-by-type "application/octet-stream" gnus-info "Corrupted" put-text-property 0 error epg-make-context epg-context-set-passphrase-callback mml2015-epg-passphrase-callback (byte-code "Ä Å\n!\"Æ" [mml2015-epg-secret-key-id-list plain child context epg-decrypt-string mm-get-part nil] 5) ((error ...)) get-buffer-create generate-new-buffer-name " *temp*" ((byte-code "Á!«Â!Á" ... 2)) search-forward "
\n" replace-match "\n" mm-dissect-buffer mm-destroy-parts epg-context-result-for verify "OK\n" mml2015-epg-verify-result-to-string "OK" get-text-property gnus-details child plain #:temp-buffer decrypt-status result inhibit-redisplay mml2015-cache-passphrase] 8)
mml2015-epg-decrypt(((#<killed buffer> ("application/pgp-encrypted") nil nil ("inline") nil nil nil) (#<killed buffer> ("application/octet-stream") nil nil ("inline") nil nil nil)) ("multipart/encrypted" (protocol . "application/pgp-encrypted") (boundary . "=-=-=")))
mml2015-decrypt(((#<killed buffer> ("application/pgp-encrypted") nil nil ("inline") nil nil nil) (#<killed buffer> ("application/octet-stream") nil nil ("inline") nil nil nil)) ("multipart/encrypted" (protocol . "application/pgp-encrypted") (boundary . "=-=-=")))
mm-possibly-verify-or-decrypt(((#<killed buffer> ("application/pgp-encrypted") nil nil ("inline") nil nil nil) (#<killed buffer> ("application/octet-stream") nil nil ("inline") nil nil nil)) ("multipart/encrypted" (protocol . "application/pgp-encrypted") (boundary . "=-=-=")) "oub(a)mat.ucm.es")
mm-dissect-multipart(("multipart/encrypted" (protocol . "application/pgp-encrypted") (boundary . "=-=-=")) "oub(a)mat.ucm.es")
mm-dissect-buffer(nil t)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(7617 nil)
gnus-summary-display-article(7617)
gnus-summary-next-page(nil)
call-interactively(gnus-summary-next-page)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Re: Latest 21.5 updates: texinfo breaks in compiling
11 years, 6 months
Stephen J. Turnbull
Robert Royar writes:
> The problem with sed/gsed is not solvable without compounding the
> issue or choosing tool names based on OS.
Well, I think my primary idea is to avoid extended REs.
However, it would also be possible to test which switch the native (=
on the default $PATH for the distro) sed accepts.
Choosing tool names based on OS probably is a bad idea; you don't know
that the non-native version will be available. (I'm sure you know
that, I'm just being complete for the archives.)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Re: Latest 21.5 updates: texinfo breaks in compiling
11 years, 6 months
Stephen J. Turnbull
Robert Royar writes:
> I pulled the changes this morning and found an error in the sed
> command for the check of makeinfo version on BSD derived systems.
> On a macports system GNU sed is gsed (/opt/local/bin/gsed).
Noted. I'm not sure what to do about it offhand; I assume it can wait
a few days.
> Similar complications arise when configure scripts assume make is
> GNU make.
True, but that ship has sailed to some extent; the packages require
GNU make, and have done so for many years.
> macports uses the 'g' prefix for the GNU tool set to allow both to
> live together.
I don't see the relevance:
$ /usr/bin/make --version
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for i386-apple-darwin10.0
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Re: Latest 21.5 updates: texinfo breaks in compiling
11 years, 6 months
Jerry James
On Tue, Jun 25, 2013 at 8:01 AM, Robert Royar <xemacs(a)royar.org> wrote:
> I think the solution
> could be to r
> equire users such as myself to use an upgraded makeinfo, or refuse to
> upgrade the docs that fail to build, but do not stop the exec build or
> installation.
> In fact, as I wrote in my initial post, I figured out the solution before I
> posted. I think configure should have figured it out for me. The errors
> would not necessarily hit one as a problem with makeinfo version.
Here's a candidate patch. Does this approach look reasonable?
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta