From 208da5f60529d3fb32dde8f8c3ce90511821cbd5 Mon Sep 17 00:00:00 2001 From: Dan Prince Date: Mon, 13 Apr 2015 13:51:51 -0400 Subject: [PATCH] Update packages earlier Turns out that updating packages last causes some pretty non-intuitive behaviour if you are trying to pin a package to a specific version. Lets just update the base RPMs first... subsequent installations should install the most updated version anyways (unless they are pinned). Also moves the package-installs script from the 00 step to 01 so we can do the update first. Co-Authored-By: Ben Nemec Change-Id: I962046cc6048e852e6582fbc579f88bb73e23fdd --- elements/base/install.d/{99-up-to-date => 00-up-to-date} | 0 .../install.d/{00-package-installs => 01-package-installs} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename elements/base/install.d/{99-up-to-date => 00-up-to-date} (100%) rename elements/package-installs/install.d/{00-package-installs => 01-package-installs} (100%) diff --git a/elements/base/install.d/99-up-to-date b/elements/base/install.d/00-up-to-date similarity index 100% rename from elements/base/install.d/99-up-to-date rename to elements/base/install.d/00-up-to-date diff --git a/elements/package-installs/install.d/00-package-installs b/elements/package-installs/install.d/01-package-installs similarity index 100% rename from elements/package-installs/install.d/00-package-installs rename to elements/package-installs/install.d/01-package-installs