Precedence: list
MIME-Version: 1.0
In-Reply-To: <20120406164641.6f7f7a74@vostro>
References: <CAML-Udub-YusXQ6xMJyWo6jMvnHO5V3u4FkkywSncPFvwfjNKg@mail.gmail.com>
	<20120406160622.2db84f05@vostro>
	<CAML-UdvATTNHzn_C2wuph5jKx1MAg5acJKJjqJTV0P5vqHsfOw@mail.gmail.com>
	<20120406164641.6f7f7a74@vostro>
Date: Fri, 6 Apr 2012 10:24:53 -0400
Message-ID: <CAML-UdsKoLm3YpKN0_u7H0TaqR6fqUTvaSgCp61Dw10SjgG+5A@mail.gmail.com>
Subject: Re: [alpine-devel] APK version formats
From: Kiyoshi Aman <kiyoshi.aman@gmail.com>
To: Timo Teras <timo.teras@iki.fi>
Cc: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset=UTF-8

2012/4/6 Timo Teras <timo.teras@iki.fi>:
> Alternative is that we change version to be just a 'display version';
> and keep the apk-tools version separate thing. I believe it was earlier
> suggested that we could just use the package source repository and
> build timestamp to decide which package is the preferred one. In this
> case we could just dump whatever garbage in the version field, ignore
> it, and figure out the preferred package from better fields.

Having a display version which can contain whatever would be ideal,
yes, provided it can be mapped to the internal version apk-tools
expects without causing problems.


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---