July 2013 - XEmacs-Beta - XEmacs Mailing List Archives

GPLv3|L8R -- Status report - ready for inspection? 7 years, 5 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

4 participants
3 comments

Re: Loading startup changes load-path? 10 years, 7 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

3 participants
6 comments

el-rcfiles v1.0 10 years, 11 months

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

3 participants
6 comments

Texinfo 5.x and the packages 11 years

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

3 participants
7 comments

Configure uses sed -rn 11 years, 3 months

Raymond Toy

In a recent update to handle the issue with makeinfo version, configure calls sed with the option -rn. On my Mac the system version of sed does not support the -rn option. While I can probably easily update my macports installation to add gnu sed, it seems that if we must use -rn, we should at least check if gnu sed is available. Ray _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
6 comments

Summary of XEmacs Issue Tracking System Issues 11 years, 3 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2013-07-23 - 2013-07-30) 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. 562 open ( +1) / 296 closed ( +0) / 858 total ( +1) Open issues with patches: 13 Average duration of open issues: 1505 days. Median duration of open issues: 1613 days. Open Issues Breakdown new 245 ( +1) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 150 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 17 ( +0) Issues Created Or Reopened (1) ______________________________ xemacs seems to mis-compile parts of vm 2013-07-29 http://tracker.xemacs.org/XEmacs/its/issue860 created anonymous _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Fwd: Bugs and patches for erc 11 years, 4 months

Johann 'Myrkraverk' Oskarsson

Hi all, I have uncovered at least two bugs in the erc package as of xemacs-sumo-2010-07-27.tar.bz2. Bug one: When logging and truncating is enabled and the the log file is smaller than erc-max-buffer-size, the log is not inserted into the buffer when joining a channel. As of bitbucket today, this is fixed by changing line 238 in erc-log.el.

1 participants
0 comments

Bugs and patches for erc 11 years, 4 months

Johann 'Myrkraverk' Oskarsson

Hi all, I have uncovered at least two bugs in the erc package as of xemacs-sumo-2010-07-27.tar.bz2. Bug one: When logging and truncating is enabled and the the log file is smaller than erc-max-buffer-size, the log is not inserted into the buffer when joining a channel. As of bitbucket today, this is fixed by changing line 238 in erc-log.el.

1 participants
0 comments

Bugs in erc (package) 11 years, 4 months

Johann 'Myrkraverk' Oskarsson

Hi all, I have uncovered at least two bugs in the erc package as of xemacs-sumo-2010-07-27.tar.bz2. Bug one: When logging and truncating is enabled and the the log file is smaller than erc-max-buffer-size, the log is not inserted into the buffer when joining a channel. As of bitbucket today, this is fixed by changing line 238 in erc-log.el.

1 participants
2 comments

Summary of XEmacs Issue Tracking System Issues 11 years, 4 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2013-07-16 - 2013-07-23) 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. 561 open ( +0) / 296 closed ( +0) / 857 total ( +0) Open issues with patches: 13 Average duration of open issues: 1501 days. Median duration of open issues: 1606 days. Open Issues Breakdown new 244 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +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

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta July 2013