X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 65898DC0182 for ; Mon, 3 Dec 2012 13:42:53 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id je9so1236467bkc.13 for ; Mon, 03 Dec 2012 05:42:52 -0800 (PST) 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=Y3BMzY47sjlBWWoClGFvHNp35xdxXS51lEvIZpkjilg=; b=b2c5yD2V+8mmDZglzck6CO7FPNhT2sHFg8fs52qTX+tIkmhAytyoa9idH3NHyWB7LJ iXb52w6stdOSGsW503W54iVoDJ8P4KwzfN4pkMiDTlHPqguDFDd3rx/AidrXIoH26HJR MwOYifJC98GdQ5+iVxC42Y/3lha5o7teDyXuvItqjcFV9bKp1UP0RakTlttEcKh87V6P MrSE2EX75nP0tb4MCy923iqoyAz576CrWM1wIgpMjVYq8Tyq8Q23ggijhp5D8bA8Bx/L 0urOVZYGzmaCdZViKmSCnwldcSVmS0YVeovJ8tRzz42jOcgnPIaeSYAtLcQjo9036ETo vSYA== Received: by 10.204.128.85 with SMTP id j21mr2853639bks.10.1354542172317; Mon, 03 Dec 2012 05:42:52 -0800 (PST) Received: from vostro ([2001:1bc8:101:f402:21c:23ff:fefc:bf0b]) by mx.google.com with ESMTPS id l17sm7321925bkw.12.2012.12.03.05.42.50 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 05:42:51 -0800 (PST) Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= Date: Mon, 3 Dec 2012 15:42:14 +0200 From: Timo Teras To: Dubiousjim Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Some questions about apk-tools Message-ID: <20121203154214.153cc8b0@vostro> In-Reply-To: <20121130153633.GJ2390@vaio.jimpryor.net> References: <20121128234406.GD2390@vaio.jimpryor.net> <20121129084044.29515fc1@vostro> <20121129124028.GE2390@vaio.jimpryor.net> <20121130154404.68b4de2a@vostro> <20121130151417.GI2390@vaio.jimpryor.net> <20121130153633.GJ2390@vaio.jimpryor.net> X-Mailer: Claws Mail 3.9.0 (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 Fri, 30 Nov 2012 10:36:33 -0500 Dubiousjim wrote: > On Fri, Nov 30, 2012 at 10:14:17AM -0500, Dubiousjim wrote: > > > > Thanks so much for these explanations. Things are a lot clearer now. > > > > On Fri, Nov 30, 2012 at 03:44:04PM +0200, Timo Teras wrote: > > > with "fix" -r is actually reinstall, the default behaviour. with > > > -d you get the fix action propagated to all dependencies. With -d > > > it would reinstall the named package and all it's dependencies. > > > > So the -r flag on fix is a noop? > > From quickly peeking at the source, it looks like: > > * `apk fix foo` and `apk fix -r foo` behave the same. Can I assume > that it's always the current version that's re-installed, even > if an upgrade is available? And that if foo isn't currently installed, > these commands do nothing? Correct. This is a legacy thing, on previous versions (alpine 2.3 and earlier), the you had to specify -r or -u. That was kinda lame to most of the time need to write the extra -r, so now it is assumed if -u is not specified. > * `apk fix -u foo` won't reinstall foo, but will install an > upgrade for foo if one is available. Correct. > > * `apk fix -r -u foo` will install an upgrade for foo if one is > available, else will reinstall the current version. Correct. > Is that right? Yes. :) - Timo --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---