1. 21 Jan, 2021 1 commit
    • Eric Timmons's avatar
      Record the source of configuration directives in the source-registry config · 61c9e3dd
      Eric Timmons authored
      The source registry configuration is described by a bunch of forms in a DSL
      that allows for inheritance. Before constructing the actual source
      registry (mapping from primary system names to pathnames), the configuration
      DSL is expanded into a list of directories to search and flattened.
      
      Previously, the flattening process left no indication of *why* a particular
      directory was being searched. We now record that information as a list of
      locations, ordered from most specific to least specific. This list can contain
      any of the following:
      
      + A symbol: The directive was generated by calling the symbol as a function
      with zero arguments.
      
      + A directory pathname: The directive came from one of the files located in
      this directory ending with .conf.
      
      + A file pathname: The directive came from the named file.
      
      + NIL: The directive came from a literal NIL (simplifies to just an inherit
      directive).
      
      + :INHERIT: The directive resulted from inheriting configuration.
      
      So a source list such as:
      (#P"/home/USER/.config/common-lisp/source-registry.conf.d/"
       USER-SOURCE-REGISTRY-DIRECTORY :INHERIT
       USER-SOURCE-REGISTRY :INHERIT
       ENVIRONMENT-SOURCE-REGISTRY :INHERIT
       NIL :INHERIT
       WRAPPING-SOURCE-REGISTRY)
      
      Should be interpretted as: The specified search directory is being searched
      because it was named in one of the files
      /home/USER/.config/common-lisp/source-registry.conf.d/*.conf, which was
      searched as part of the user's source registry directory, which was included
      because the user's source registry conf file was empty or included a
      :inherit-configuration directive, which was included because CL_SOURCE_REGISTRY
      was parsed to something that contained a :inherit-configuration directive,
      which was included because the user did not manually specify a configuration to
      use, which was then included by the wrappign source registry which can never be
      overridden.
      61c9e3dd
  2. 30 Nov, 2020 2 commits
  3. 29 Nov, 2020 3 commits
  4. 28 Nov, 2020 6 commits
  5. 25 Nov, 2020 4 commits
  6. 20 Nov, 2020 3 commits
  7. 19 Nov, 2020 2 commits
  8. 18 Nov, 2020 3 commits
  9. 17 Nov, 2020 1 commit
    • Gary Palter's avatar
      Fix bug which causes compilation to leave empty temporary files on Genera · 6cc44d02
      Gary Palter authored and Robert Goldman's avatar Robert Goldman committed
      Genera uses versioned pathnames. TMPIZE-PATHNAME creates a temporary file
      to ensure a unique name. If we leave that file, Genera will create a new
      version (i.e., version 2) when its caller opens the file for output. After
      that file is renamed, the original temporary file remains. Since Genera runs
      on a single core processor, the possibility of a name collision is minimal
      if not nil. So, don't keep the temporary file.
      6cc44d02
  10. 16 Oct, 2020 2 commits
  11. 09 Sep, 2020 1 commit
  12. 27 Jun, 2020 1 commit
  13. 26 May, 2020 2 commits
    • Robert Goldman's avatar
      Bump version to 3.3.4.5 · b17c089c
      Robert Goldman authored
      b17c089c
    • Robert Goldman's avatar
      Fix for issue #34. · 450f759f
      Robert Goldman authored
      Jingtao Xu discovered that package-inferred-system's could not handle
      files with different extensions, because the "lisp" extension was
      hard-coded into the system search function for
      package-inferred-system's.
      
      This commit fixes that issue and adds a test.  Thanks to Jingtao Xu
      for the fix.
      450f759f
  14. 15 May, 2020 2 commits
  15. 30 Apr, 2020 2 commits
    • Robert Goldman's avatar
      Bump version to 3.3.4.4 · afd58f91
      Robert Goldman authored
      afd58f91
    • Robert Goldman's avatar
      Ignore spurious errors in SBCL compilation. · 2411d116
      Robert Goldman authored
      Ignore errors in sb-grovel-unknown-constant-condition-p.
      
      An error is raised if `simple-condition-format-control` is a formatter
      functionand is is passed to `string`. This now mirrors
      `match-condition-p` which also ignores errors when comparing a simple
      condition to a string.
      
      Test added to test-utilities.script for this issue.
      
      Thanks to Eric Timmons for the fix.
      2411d116
  16. 29 Apr, 2020 4 commits
  17. 28 Apr, 2020 1 commit