1. 01 Jan, 2020 1 commit
  2. 01 Jan, 2019 1 commit
  3. 01 Jan, 2018 1 commit
  4. 13 Sep, 2017 1 commit
    • Paul Eggert's avatar
      Prefer HTTPS to FTP and HTTP in documentation · bc511a64
      Paul Eggert authored
      Most of this change is to boilerplate commentary such as license URLs.
      This change was prompted by ftp://ftp.gnu.org's going-away party,
      planned for November.  Change these FTP URLs to https://ftp.gnu.org
      instead.  Make similar changes for URLs to other organizations moving
      away from FTP.  Also, change HTTP to HTTPS for URLs to gnu.org and
      fsf.org when this works, as this will further help defend against
      man-in-the-middle attacks (for this part I omitted the MS-DOS and
      MS-Windows sources and the test tarballs to keep the workload down).
      HTTPS is not fully working to lists.gnu.org so I left those URLs alone
      for now.
      bc511a64
  5. 01 Jan, 2017 1 commit
  6. 01 Jan, 2016 1 commit
  7. 11 Oct, 2015 1 commit
    • Paul Eggert's avatar
      Use ‘echo’ safely with ‘\’ or leading ‘-’ · 29dfca23
      Paul Eggert authored
      POSIX says that ‘echo FOO’ produces implementation-defined output
      if FOO contains leading ‘-’, or ‘\’ anywhere, so don’t assume GNU
      behavior in that case.
      * Makefile.in (removenullpaths): Remove.
      (epaths-force): Rewrite to avoid the need for ‘echo’.
      (install-etc): Be clearer about escaping the shell metacharacters
      ‘\’ and ‘$’.
      * Makefile.in (install-arch-indep, install-etcdoc):
      * admin/charsets/mapconv, admin/merge-gnulib, admin/merge-pkg-config:
      * admin/quick-install-emacs, build-aux/gitlog-to-emacslog:
      * configure.ac, lib-src/rcs2log, make-dist:
      * src/Makefile.in (lisp.mk):
      Don’t assume ‘echo’ outputs ‘\’ and leading ‘-’ unscathed.
      For example, use ‘printf '%s\n' "$foo"’ rather than ‘echo "$foo"’
      if $foo can contain arbitrary characters.
      * lisp/Makefile.in (TAGS): Use ‘ls’, not ‘echo’, to avoid ‘\’ issues.
      * doc/lispref/two-volume.make (vol1.pdf):
      * test/etags/make-src/Makefile (web ftp publish):
      Use ‘printf’ rather than ‘echo -e’.
      29dfca23
  8. 01 Jan, 2015 1 commit
  9. 16 May, 2014 1 commit
    • Paul Eggert's avatar
      Don't require pkg-config when building from repository. · c56327b5
      Paul Eggert authored
      * INSTALL: Prefer './configure FOO=BAR' to 'FOO=BAR ./configure'.
      * INSTALL.REPO: pkg-config is no longer required to build from
      the repository.
      * autogen.sh: Don't check for pkg-config.
      (progs): Remove pkg-config.
      (pkg_config_min, AUTORECONF_ENV, env_space, ACLOCAL_PATH):
      Remove.  All uses removed.
      * m4/pkg.m4: New file, built by admin/merge-pkg-config.
      * configure.ac: Remove unnecessary m4_pattern_forbid of ^PKG_ and
      an AC_ARG_VAR of PKG_CONFIG_PATH.  pkg.m4 does that for us.
      (EMACS_CHECK_MODULES): Remove workaround for old pkg-config bug,
      as we use pkg.m4 from a newer pkg-config.
      * admin/merge-pkg-config: New script.
      * admin/notes/copyright: Update for m4/*.m4, in particular m4/pkg.m4.
      * etc/NEWS: Prefer './configure FOO=BAR' to 'FOO=BAR ./configure'.
      * etc/PROBLEMS (Build-time-problems): Remove pkg-config problem
      that is no longer an issue.
      * nt/INSTALL: Remove no-longer-needed notes about pkg-config.
      c56327b5