Date: Mon, 29 Oct 2012 14:17:37 -0400
From: Dubiousjim <lists+alpine-devel@jimpryor.net>
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] Questions about apk CMD -U
Message-ID: <20121029181737.GB16841@vaio.jimpryor.net>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

I'm doing some wiki cleanup, and have come across some issues I don't
know the answer to. Can someone please clarify what is the EXACT effect
of the -U/--update-cache flag for apk in each of the following
circumstances:

1. apk update -U (with an APK package cache enabled? without?)
2. apk add -U  (with an APK package cache enabled? without?)
3. apk upgrade -U (with an APK package cache enabled? without?)

I assume that the -U flag in cases 2 and 3 makes it unnecessary to first
run an "apk update". Is that correct? Is the -U flag in case 1 a no-op?
Does the -U flag ever run an implicit "apk cache download", or anything
of that sort?

If anyone remembers at which earlier points in Alpine history the present behaviors became
available, and what the preceding behavior was, that may also help with
some wiki pages describing how to upgrade from older systems. For
example, at which point could one begin relying on apk to upgrade
apk-tools first, if necessary?

-- 
Dubiousjim
dubiousjim@gmail.com


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---