Skip to content
Snippets Groups Projects
  1. Feb 11, 2012
  2. Feb 10, 2012
    • Nat Goodspeed's avatar
      Eliminate ManifestError for wildcards matching 0 files. · acd46062
      Nat Goodspeed authored
      Turns out that some (many?) wildcard LLManifest.path(wildcard) calls are "just
      in case": sweep up any (e.g.) "*.tga" files there may be, but no problem if
      there are none.
      Change path() logic so it tries the next tree (source, artwork, build) if
      either a specific (non-wildcard) filename doesn't exist, as now, OR if a
      wildcard matches 0 files in the current tree. This continues to support "just
      in case" wildcards, while permitting wildcards to work in the artwork and
      build trees as well as the source tree.
      Use a more specific exception than ManifestError for missing file. Only in
      that case should we try the next tree. Any other ManifestError should
      propagate.
      acd46062
    • Nat Goodspeed's avatar
      Try using Log's new APR packages for Windows, Mac, Linux. · 9011b044
      Nat Goodspeed authored
      This APR merges work from Huseby, Log, Leslie, Nat.
      9011b044
    • Nat Goodspeed's avatar
    • Nat Goodspeed's avatar
      Use wildcards instead of many version-specific lib names on Linux. · 028a05e7
      Nat Goodspeed authored
      viewer_manifest.py's Linux_i686Manifest class has contained directives to copy
      library files with names like (e.g.) "libapr-1.so.0.4.2", which means that
      every update to any such library requires messing with viewer_manifest.py.
      But LLManifest.path() claims to support wildcards, and it's more robust to
      specify "libapr-1.so*" instead.
      Unfortunately LLManifest.path()'s wildcard support only used to work for files
      in the source tree (vs. the artwork tree or the build tree). The logic in
      path() tries each tree in turn, relying on an exception to make it try the
      next tree. This exception was raised for a nonexistent specific filename --
      but it never used to raise that exception for a wildcard matching 0 files.
      Instead it would simply report "0 files" and proceed, producing an invalid
      viewer install.
      Raise that exception for a wildcard matching nothing. This forces path() to
      consider the artwork tree and the build tree, permitting us to use wildcards
      in library names.
      Define an exception specific to LLManifest: ManifestException rather than the
      generic Python RuntimeException. Make it a subclass of RuntimeException so any
      existing callers expecting to catch RuntimeException will continue to work.
      028a05e7
  3. Feb 09, 2012
  4. Feb 06, 2012
  5. Feb 03, 2012
  6. Feb 01, 2012
  7. Jan 30, 2012
  8. Jan 25, 2012
  9. Jan 24, 2012
  10. Jan 30, 2012
  11. Jan 24, 2012
  12. Jan 23, 2012
  13. Jan 20, 2012
Loading