* New Package: svn2git
https://github.com/nirvdrum/svn2git
svn2git is a tiny utility for migrating projects from Subversion to Git while
keeping the trunk, branches and tags where they should be. It uses git-svn to
clone an svn repository and does some clean-up to make sure branches and tags
are imported in a meaningful way, and that the code checked into master ends up
being what's currently in your svn trunk rather than whichever svn branch your
last commit was in.
* Actually requires +perl variant of subversion.
* fix style issue.
* Added magma package
* Incorporated Serban's change
* Remove deleted files
* argparse.py
* Sync forked Spack repo in github
* Use reported version of IBM XL Fortran compiler for compiler versions
>= 16.0.
Starting with the April 2018 release, the IBM XL C and Fortran
compilers report the same version, 16.0. Consequently, there is
no need to downgrade the Fortran compiler version to match that
of the C compiler.
* Eliminate blank lines.
* Update the Spectrum MPI package.py file to specify the correct compilation
scripts for the PGI compilers.
* mvapich2: add registration cache and file systems variants, avoid empty --with-pm= if no process manager is specified, add missing leading dash in --disable-silent-rules
* mpifileutils: roll back to dtcmp v1.0.3 due to API change, add option to build master branch
* add comment to explain why certain dtcmp is required, rename version for git branch
* dtcmp v1.0.2 is missing github tarball
When building eospac with %clang, spack's Fortran compiler wrapper is called
'flang', which is rejected by the eospac build system..Allow compilation with
%clang by patching the eospac build system.
My testing only covers %clang where flang is actually gfortran. However, this
patch only registers 'flang' as a known Fortran compiler and does not set any
flags or options that are compiler specific.
.
Add configurable HTTP, Python and readline support.
Add previously missing dependencies.
Minor patch to improve Python support (see https://github.com/xrootd/xrootd/pull/695).
* Use GitLab's API endpoint for fetching a git snapshot.
* More GitLab packages use the API.
* find_list_url for GitLab's API URLs.
* Flake8
* Url for 'hacckernels'.
* Check GitLab API regexps before the non-API ones.
* Add Trinity package
New package to install Trinity - another odd installer (assumes installation to /usr/local/bin and doesn't copy dot files hence deleting them)
* Update package.py
added dependencies from https://github.com/trinityrnaseq/trinityrnaseq/wiki/Installing-Trinity
* Update package.py
Copy tree to prefix.bin so that PATH can correctly be set for the Trinity command - can't split it off as it seems everything needs to stay together.
* Update package.py
Fixed over-length lines and space before comma
This commit fixes#7900.
In short: in the absence of constraints to the contrary, spack will
download the preferred version of a package, which is usually the most
recent non-develop version. On a clean spack installation without
hypre installed, `spack install mfem` will download hypre 2.14.0,
which is API-incompatible with mfem 3.3.2 (and earlier versions of
mfem), so spack will throw compiler errors re: the API mismatch.
This commit fixes that error by restricting mfem release versions
3.3.2 and earlier to hypre version 2.10.b to 2.13.999 (only 2.13.0
currently exists, but if it has a non-2.14.x maintenance release,
these versions of hypre should also be permitted).
