X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id E2CA7DC00BA for ; Mon, 29 Oct 2012 19:15:55 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BBCFE201A7; Mon, 29 Oct 2012 15:15:54 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 29 Oct 2012 15:15:54 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=+caKur0PzjWoo9es65lGcI4ARcQ=; b=LOlenTOOvXsBLPHwDRNJstcSX+it MfLu51wYar/rwVC2ePuNkRBdz5wrLva0DwugJpQaQ+dTjczOWYO4MMbZgV0Bmu52 Rryn7jd0GIns41uvfWm8pdVwHGn4Wi4koM9y5HQR40TCtxxwfuAwIjzUK+YMZrxd r3/a9p/uIi9xylc= X-Sasl-enc: F/txuChsyakeSsfZ7/riWdoRoXCd9x0VzJnaf4P8rzfX 1351538154 Received: from localhost (unknown [69.86.161.234]) by mail.messagingengine.com (Postfix) with ESMTPA id 640F64824A0; Mon, 29 Oct 2012 15:15:54 -0400 (EDT) Date: Mon, 29 Oct 2012 15:15:24 -0400 From: Dubiousjim To: Timo Teras Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Questions about apk CMD -U Message-ID: <20121029191524.GC16841@vaio.jimpryor.net> References: <20121029181737.GB16841@vaio.jimpryor.net> <20121029204343.501bef56@vostro> 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-Disposition: inline In-Reply-To: <20121029204343.501bef56@vostro> User-Agent: Mutt/1.5.21 (2010-09-15) On Mon, Oct 29, 2012 at 08:43:43PM +0200, Timo Teras wrote: > the -U flag always does the one and same thing. It executes > "apk update" > before running the real command. > > ... > > 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. Thanks Timo, this enabled me to fix some confusing/incorrect statements in the wiki. (Some but not all introduced by me.) The "apk add asterisk=1.6.0.21-r0" and "apk add 'asterisk<1.6.1'" syntax is already described at http://wiki.alpinelinux.org/wiki/Alpine_Linux_package_management I'm not familiar with the "apk add foo@edge" syntax. What if my /etc/apk/repositories file looks like this: /var/lib/packages/main /var/lib/packages/testing http://nl.alpinelinux.org/alpine/edge/main http://nl.alpinelinux.org/alpine/edge/testing I assume that the "... foo@edge" syntax will force whatever foo package is in one of the last two repositories to be counted as most recent. But which one? Does it look at both of them? What else is usable in the "@edge" position of "foo@edge"? I assume "@v2.4" is also usable. What about "@main" or "@testing"? If you want to point me to the release notes describing this functionality, or write up a quick explanation, I'll be glad to format it and merge it into the wiki. -- Dubiousjim dubiousjim@gmail.com --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---