DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=e9zL/eKLpIwW4XFnz8RAQyrTzwU38J2Bw2KoTCjoddlrulRz/GNSYm8y3YEc6New3B
         DwsQutAENQvyYfEtCZlCRgL0RiTx7UKFBkhyBITF2hdVNt6yJ7zZ5rNVUWo2eLiLcd5G
         zWQeabI9z4GObGRoSLqONlxY5fitIky+OAzqA=
Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Message-ID: <4C7FB583.2050506@iki.fi>
Date: Thu, 02 Sep 2010 17:32:35 +0300
From: =?UTF-8?B?VGltbyBUZXLDpHM=?= <timo.teras@iki.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100713 Thunderbird/3.0.6
Precedence: list
MIME-Version: 1.0
To: Natanael Copa <ncopa@alpinelinux.org>
CC: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] RFC: how to deal with /etc/alpine-release
References: <1283434091.1942.110.camel@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <1283434091.1942.110.camel@ncopa-desktop.nor.wtbts.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 09/02/2010 04:28 PM, Natanael Copa wrote:
> Currently, the alpine-release is a symlink to a raw file on the cdrom.
> once you have installed to disk the /etc/alpine-release link is broken.
> 
> I wonder how we deal with this?
> 
> Other options or ideas?

Well, apk package index also provides similar information now. Apk could
update it on 'apk update' or 'apk upgrade' or so.

- Timo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---