diff options
Diffstat (limited to 'source/updating.rst')
| -rw-r--r-- | source/updating.rst | 26 |
1 files changed, 7 insertions, 19 deletions
diff --git a/source/updating.rst b/source/updating.rst index f897e2c..24e0018 100644 --- a/source/updating.rst +++ b/source/updating.rst @@ -2,9 +2,7 @@ Keeping AstroConda "Like New" ***************************** -Anaconda's package manager, Conda, will not automatically update unless a newer version of a package is detected during -a routine package installation. Suffice to say, unless you keep your packages up to date with ``conda update``, the -packages installed in your Anaconda distribution will remain relatively static. +Anaconda's package manager, Conda, will not automatically update unless a newer version of a package is detected during a routine package installation. Suffice to say, unless you keep your packages up to date with ``conda update``, the packages installed in your Anaconda distribution will remain relatively static. Updating AstroConda =================== @@ -18,10 +16,7 @@ Updating the Release $ conda update -n astroconda stsci -This is best used by individuals that favor software stability over receiving the "bleeding edge". Remember, updating the -``stsci`` metapackage only effects packages part of the **official public release** of our software. Packages that are -provided by the AstroConda repository, but are not controlled by the ``stsci`` metapackage **will not receive updates**. -This holds true for all other metapackages as well (e.g. stsci-hst, stsci-jwst, stsci-data-analysis, etc). +This is best used by individuals that favor software stability over receiving the "bleeding edge". Remember, updating the ``stsci`` metapackage only effects packages part of the **official public release** of our software. Packages that are provided by the AstroConda repository, but are not controlled by the ``stsci`` metapackage **will not receive updates**. This holds true for all other metapackages as well (e.g. stsci-hst, stsci-jwst, stsci-data-analysis, etc). Updating All Packages --------------------- @@ -32,8 +27,7 @@ Updating All Packages This will update the ``stsci`` metapackage, as well all other packages installed in your enviroment. [1]_ -This updates **all packages** regardless if they were installed from AstroConda, Continuum, Inc., -or other third party repositories defined in ``$HOME/.condarc``. +This updates **all packages** regardless if they were installed from AstroConda, Continuum, Inc., or other third party repositories defined in ``$HOME/.condarc``. (`ref <http://conda.pydata.org/docs/using/pkgs.html#package-update>`__) @@ -45,15 +39,13 @@ Updating Packages Individually $ conda update -n astroconda stsci.tools -If you are interested in receiving updates for a particular package, then this method is for you. Be aware that packages -may depend on other packages, so the total list of package updates returned by this command will vary. +If you are interested in receiving updates for a particular package, then this method is for you. Be aware that packages may depend on other packages, so the total list of package updates returned by this command will vary. Downgrading Packages ==================== -Did a recent update break your code? Don't wait around for a bugfix... Keep working. For example, if a bug is introduced -into ``stsci.tools``, you can easily downgrade it to a known-good version: +Did a recent update break your code? Don't wait around for a bugfix... Keep working. For example, if a bug is introduced into ``stsci.tools``, you can easily downgrade it to a known-good version: .. code-block:: sh @@ -79,18 +71,14 @@ Pinning Packages .. caution:: Pinning packages has the potential to break Conda. Only pin packages as a last resort. -Let's take the previous example one step further... Imagine ``stsci.tools`` is broken, and the hotfix release of ``3.4.2`` -only partially solved the original issue. Now what? You still need to receive updates to other packages, but -``stsci.tools`` keeps trying to update back to ``3.4.2`` every time you touch ``conda update``. +Let's take the previous example one step further... Imagine ``stsci.tools`` is broken, and the hotfix release of ``3.4.2`` only partially solved the original issue. Now what? You still need to receive updates to other packages, but ``stsci.tools`` keeps trying to update back to ``3.4.2`` every time you touch ``conda update``. .. code-block:: sh $ echo "stsci.tools <=3.4.0" > ${CONDA_ENV_PATH}/conda-meta/pinned -From now on, future calls to ``conda update`` will omit ``stsci.tools`` while performing dependency resolution. However, -a clear side-effect of this will also be losing the ability to update packages that depend strictly on version ``3.4.2``. -Although this is not a permanent solution it can prove useful in a bad situation. +From now on, future calls to ``conda update`` will omit ``stsci.tools`` while performing dependency resolution. However, a clear side-effect of this will also be losing the ability to update packages that depend strictly on version ``3.4.2``. Although this is not a permanent solution it can prove useful in a bad situation. (`ref <http://conda.pydata.org/docs/faq.html?highlight=pinning#pinning-packages>`__) |