X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id C9696DC00B7 for ; Mon, 29 Oct 2012 18:45:03 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c50so2848524eek.13 for ; Mon, 29 Oct 2012 11:45:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:in-reply-to:references :x-mailer:mime-version:content-type:content-transfer-encoding; bh=bUvjmK1P6nQaHdoUFoe5IbFSIpP0XN1rT7VNWYhMUyM=; b=uRUYAvcNHS8uvkbXYvDeebay2T6JcrYoSlY9/LYhh6+76Au3NBxHfYh5QRLEe7wKJy KS3knu3SfSBS1Mp/EkS945yOOTuNh6WaKUUwg0o+n196lRH07k0/t9xeF27M2RfldPpj ULlyN8H2UNbNPXAuNDGArfU3s5vNYRu/bKI4PsU36LzDF8eFBfC7npA/3qbo0rIbAtYY rrJl9BJgNOrssCdlE+GGLnsbEZaEG4+t7HdbID0V7v3j4zzPjM9wv/1HwvxZ1++DzJz/ i3hkL3peWyUgC5+w7ODhh2HSSEH000dK9INTJQuFdUyRof6YOoPLNag6tOu68PuADhy0 5UGw== Received: by 10.14.194.71 with SMTP id l47mr63495231een.6.1351536301809; Mon, 29 Oct 2012 11:45:01 -0700 (PDT) Received: from vostro ([2001:1bc8:101:f402:21c:23ff:fefc:bf0b]) by mx.google.com with ESMTPS id g5sm24363852eem.4.2012.10.29.11.45.00 (version=SSLv3 cipher=OTHER); Mon, 29 Oct 2012 11:45:01 -0700 (PDT) Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= Date: Mon, 29 Oct 2012 20:43:43 +0200 From: Timo Teras To: Dubiousjim Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Questions about apk CMD -U Message-ID: <20121029204343.501bef56@vostro> In-Reply-To: <20121029181737.GB16841@vaio.jimpryor.net> References: <20121029181737.GB16841@vaio.jimpryor.net> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; i686-pc-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 29 Oct 2012 14:17:37 -0400 Dubiousjim wrote: > 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? the -U flag always does the one and same thing. It executes "apk update" before running the real command. So "apk update -U" is redundant and -U does there nothing. > 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? commit 59d222d - upgrade: perform upgrade of apk-tools first if available is dated Sat Jan 1 15:48:10 2011 +0200 which is first included in apk-tools version 2.1.0. So the feature was first present in Alpine Linux 2.3.0_rc1. If you are updating the apk-tools wiki page, please describe the package "pinning" syntax too. This is the "apk add foo@edge" style syntax. -Timo --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---