Disable Day 2 sections and rewrite basics around %c,cxx

Author: alecbcs

outputs/Makefile

@@ -42,12 +42,12 @@ run-stacks: run-environments stacks.sh
 run-environments: run-basics environments.sh
 run-basics: basics.sh init_spack.sh defs.sh
 
-local: local-scripting
-local-scripting: local-dev scripting.sh
+local: local-environments
+# local-scripting: local-dev scripting.sh
 # local-cache: local-dev cache.sh
-local-dev: local-packaging dev.sh
-local-packaging: local-stacks packaging.sh
-local-stacks: local-environments stacks.sh
+# local-dev: local-packaging dev.sh
+# local-packaging: local-stacks packaging.sh
+# local-stacks: local-environments stacks.sh
 local-environments: local-basics environments.sh
 local-basics: basics.sh init_spack.sh defs.sh
 

tutorial_basics.rst

@@ -224,7 +224,13 @@ Compilers are providers for virtual packages like ``c``, ``cxx``, and ``fortran`
 Because these are often provided by the same package but we might want to use C and C++ from one compiler and Fortran from another, we need a syntax to specify which virtual a package provides.
 We call this "virtual assignment", and can be specified by ``%virtual=provider`` or ``^virtual=provider``.
 
-We will now install HDF5 with MPI support provided by MPICH, ensuring that the C component of HDF5 is compiled with ``gcc``.
+For example if we wanted to install hdf5 using GCC for the C and C++ components but Intel OneAPI for the Fortran compiler we could write:
+
+.. code-block:: none
+
+   hdf5 %c,cxx=gcc %fortran=oneapi
+
+However, we'll keep it simple for now and install HDF5 with MPI support provided by MPICH.
 We could use the same syntax for ``^mpi=mpich``, but there's no need because the only way for ``hdf5`` to depend on ``mpich`` is to provide ``mpi``.
 This is also why we didn't care to specify which virtuals ``gcc`` and ``clang`` provided earlier when building simpler packages.