[Pkg-jed-commit] [SCM] Debian packaging of JED branch, jo-0.99.19, updated. 1%3A0.99.18+dfsg.1-10-178-gbb38541

Mon May 19 16:07:03 UTC 2008

The following commit has been merged in the jo-0.99.19 branch:
commit cf86ccd16ea36c56acb77dac51a6c003e1490ecb
Author: Jörg Sommer <joerg at alea.gnuu.de>
Date:   Sun May 18 19:09:19 2008 +0200

    Remove README.Debian-sarge-upgrade
    
    The upgrade from sarge is long ago and we don't support upgrades from
    oldstable.

diff --git a/debian/README.Debian-sarge-upgrade b/debian/README.Debian-sarge-upgrade
deleted file mode 100644
index 2c8edb3..0000000
--- a/debian/README.Debian-sarge-upgrade
+++ /dev/null
@@ -1,120 +0,0 @@
-=========================================
-Recent changes to the Debian jed packages
-=========================================
-
-This is a listing of most important changes to the Debian Jed packages
-intended for people upgrading from Sarge (0.99.16-5).
-
-See "changelog.Debian.gz" for a detailled list of Debian specific changes
-and "changelog.gz" for the upstream changes.
-
-Packages and contents
----------------------
-
-* The jed-sl package is dropped. jed-common contains the SLang source of the
-  runtime files. During the installation of jed or xjed the *.sl
-  files will be converted to *.slc files (preparsed).
-
-* new executable jed-script (similar to jed -batch but sets the BATCH
-                             variable to 2 and doesnot run the config
-                             scripts in /etc/jed.d/)
-
-* removed executable jgrep  (did not compile cleanly)
-
-S-Lang Version 2
-----------------
-
-* Jed now uses S-Lang Version 2. There are incompatibilities that
-  break some home-made or downloaded extensions made for Slang-1.
-  This affects also several scripts in the jed-extra (1.0) package!
-
-  New features and upgrade information for version 2 are described in
-  appendix A. "S-Lang 2 Interpreter NEWS" of
-  /usr/share/doc/libslang2/slang.txt.
-
-UTF 8 support
--------------
-
-* Unicode via the UTF-8 encoding is available for jed versions 0.99-17
-  and greater that use slang2.
-
-  This feature is new and still in beta stage. Not all library
-  functions are tested with UTF-8 so expect some "teething problems".
-
-* Enabling UTF-8 support: If the locale indicates that the character set is
-  UTF-8, then UTF-8 mode will be enabled.
-
-  Examples:
-
-    Start xjed in UTF-8 mode:     LANG=de_DE.UTF-8; xjed
-    Start jed in non-UTF-8 mode:  LANG=de_DE; jed
-
-    ~/.bashrc alias:              alias ujed="LANG=de_DE.UTF-8; xjed"
-
-  There is no provision for enabling or disabling UTF-8 support during
-  runtime.
-
-  More details under the menu topic
-
-    Help>Browse_Docs utf8
-
-Jed_Home_Directory
-------------------
-
-* If the directory "~/.jed/" exists, it will become the `Jed_Home_Directory'
-  and Jed will no longer search for "~/.jedrc" at startup.
-
-  The user needs to move an eventually existing "~/.jedrc" to
-  "~/.jed/jed.rc" ("~/.jed/.jedrc" is still found but deprecated).
-
-* However, Jed will not create such a directory. Users are encouraged to
-  create the directory ".jed/" in their home directory and move an
-  eventually existing ~/.jedrc to ~/.jed/jed.rc (and ~/.jedrecent to
-  ~.jed/.jedrecent).
-
-Motivation
-''''''''''
-
-Debian Jed now supports a per-user "~/.jed/" application directory in
-accordance with the file hierarchy standard (FHS 2.3).
-
-  User specific configuration files for applications are stored in the
-  user's home directory in a file that starts with the '.' character (a
-  "dot file"). If an application needs to create more than one dot file
-  then they should be placed in a subdirectory with a name starting with
-  a '.' character, (a "dot directory"). In this case the configuration
-  files should not start with the '.' character.
-
-Debian Jed startup scheme
--------------------------
-
-* The Jed config directory is renamed from "/etc/jed-init.d/" to
-  "/etc/jed.d".
-
-  If there are files in "/etc/jed-init.d/" that are unknown to jed-common,
-  the old directory will remain in place (but not used). The sysadmin should
-  check, manually delete remaining files or move them to "/etc/jed.d" and
-  delete "/etc/jed-init.d/".
-
-  An example are the files 05home-lib.sl and 55ispell.sl installed by the
-  jed-extra (1.0) package. These will no longer be evaluated at startup
-  after the upgrade to jed (0.99.18). (The upcoming jed-extra (2.1) will
-  replace them with the new initialization file /etc/jed.d/50jed-extra.sl.)
-
-* The file "/etc/jed.conf" has been removed.
-
-  "/usr/share/jed/lib/defaults.sl" contains the code to evaluate the files
-  in "/etc/jed.d".
-
-  "/etc/jed.d/05jed-common.sl" contains the site-wide configuration for
-  jed|xjed.
-
-* Evalutation of "/etc/jed.d/" can be suppressed by the
-  --skip-debian-startup command line option.
-
-* "/etc/jed.d/" is not evaluated if Jed is started as `jed-script`.
-
-  If a script depends on the Debian configuration, it can use the function
-  debian_startup() (defined in defaults.sl) or be called with jed -batch.
-
-For details see README.Debian-startup.
diff --git a/debian/changelog b/debian/changelog
index 3bd7a27..f50b242 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -23,6 +23,10 @@ jed (1:0.99.19~pre129-1) UNRELEASED; urgency=low
     ‘Using DEB_BUILD_OPTIONS’ at
     http://wiki.debian.org/Embedded_Debian_packaging_rules
 
+  * Removed README.Debian-sarge-upgrade, because the upgrade from sarge
+    to etch happend long time ago and we don't support upgrade from other
+    than the last stable release.
+
  -- Jörg Sommer <joerg at alea.gnuu.de>  Thu, 01 Jan 1970 00:00:00 +0000
 
 jed (1:0.99.19~pre117-1) experimental; urgency=low

-- 
Debian packaging of JED

