pip install firedrake

[connorjward]

Die firedrake-install! Die! Die! Die!

Remaining tasks

• Decide what to do about make check

User-facing changes

pip install firedrake

• Changes the officially supported installation method for Firedrake to using pip.
• Adds a firedrake-configure script to facilitate installation.
• firedrake-install/firedrake-update remain but spit out a deprecation warning.
• Updates the install page to describe the new approach.
• firedrake-install --doi will no longer work.

Docker

• firedrake-vanilla and firedrake-complex have been renamed to firedrake-vanilla-default and firedrake-vanilla-complex respectively.
• firedrake is now installed directly in the container. It is no longer necessary to activate a virtual environment.
• The firedrake repository is now installed in ~/firedrake instead of ~/firedrake/src/firedrake. The same applies to other packages like gusto and thetis inside the firedrakeproject/firedrake container.
• The Docker containers now ship OpenMPI instead of MPICH. This means that running parallel tests alongside serial ones with a single pytest invocation will no longer work.
• VTK is no longer installed by default into the firedrake-vanilla containers. If your package needs it then please add it to your own pyproject.toml or run pip install vtk.

Please see firedrakeproject/gusto#618 as an example switching a workflow to using the new containers.

Developer-facing changes

• The firedrake-env container no longer contains PETSc, which is instead built in firedrake-vanilla.
• CI now rebuilds PETSc every time instead of pre-building it inside the firedrake-env container.
• The linting and zenodo canary workflows have been merged into the same workflow file as the Firedrake tests. This means that we will get fewer notifications if (when) things fail.

Design choices

Unlike firedrake-install, firedrake-configure is designed to be very, very dumb. All it does is take in a specification of a desired package manager (apt-x86_64, apt-aarch64, brew-arm64) and "arch" (default or complex) and spits out a string of appropriate system dependencies (--show-system-dependencies) or PETSc configure options (--show-petsc-configure-options). You can also pass --no-package-manager if you aren't using a supported system and this will give you a set of PETSc configure options where everything is downloaded.

[github-actions]

	Tests	Passed ✅	Skipped ⏭️	Failed ❌
Firedrake complex	8314 ran	6614 passed	1700 skipped	0 failed

[github-actions]

	Tests	Passed ✅	Skipped ⏭️	Failed ❌
Firedrake real	0 ran	0 passed	0 skipped	0 failed

[JHopeCollins]

Suggested change

	if package_manager == MACOS_HOMEBREW_ARM64:
	vars["HDF5_DIR"] = "/opt/homebrew"
	if package_manager == MACOS_HOMEBREW_ARM64:
	vars["HDF5_DIR"] = "/opt/homebrew"
	elif package_manager is None:
	vars["HDF5_DIR"] = vars["PETSC_DIR"]+"/"+vars["PETSC_ARCH"]

If --no-package-manager is used then PETSc will be told to download hdf5, and HDF5_DIR must be set so h5py knows where to link against.