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:content-type:content-transfer-encoding;
        b=TFBmTC/L9c4q8KasPJ0ejoi4LyTEUJTqLzHdaLW4hqhkxZCN5WgHuWAKM0LBJzFagi
         kBDS/JIY2C6le/FcPqn97af9/0cqBU1uXrewO4rBqbCuMekQLTCSmctXO3TvO68EXPjf
         7KCefAl7c8x+Ou/SH1AyES48OHfv5yg/GIIBE=
Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Message-ID: <4A7A8601.40007@iki.fi>
Date: Thu, 06 Aug 2009 10:28:01 +0300
From: =?ISO-8859-1?Q?Timo_Ter=E4s?= <timo.teras@iki.fi>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
Precedence: list
MIME-Version: 1.0
To: Mark Constable <markc@renta.net>
CC: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] mrxvt
References: <4A743D6D.3080100@renta.net>
In-Reply-To: <4A743D6D.3080100@renta.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mark Constable wrote:
> FWIW
> 
> % cat eth-os/mrxvt/APKBUILD
> # Contributor: Mark Constable <markc@renta.net>
> # Maintainer: Mark Constable <markc@renta.net>
> pkgname=mrxvt
> pkgver=0.5.4
> pkgrel=$(date -u +%Y%m%d%H)

I think this was already discussed to some degree earlier.
But here's my 2cents.

Generally I think having volatile pkgrel is a bad idea. The whole
idea of aports git tree is that, you can take the aports git commit
id or tag, and immediately know which packages it contains. This
breaks that. (And obviously is broken if you build the same package
twice within an hour.)

However, we do need better way to address pkgrel. E.g. we do need
some way to have svn/git APKBUILDs that automatically just take
the source head, and produce a package. So I'm wondering if we should:
1. have a "volatile" repository with APKBUILDs like this
2. have a script that automatically bumps up the pkgrel's based
   on what's available (it could even generate it from svn revision
   or git-describe) and commit it to aports
3. have a "master timestamp" to which all APKBUILDs base their
   code checkouts. so refreshing the entire system is just changing
   one file.

- Timo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---