DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date
         :message-id:mime-version:x-mailer:content-transfer-encoding;
        b=xQRqzux3i4+prZm23pwPmPSYEJoslBk6YY9jMY9qpbtpWt4bE99pmFiB2z3Mbr/tSi
         3R2QP+4l6VIZGQ3KCIxzjBErL0UkixN5qzUrjBfNUWnCzg/D+v25ppsF2TfIf1+/vX8b
         IRH6e79/LP/BsjQPhZj3CgRuVcJJ37XfOt9dc=
Subject: Re: [alpine-devel] Bumping version for acf-skins
From: Natanael Copa <natanael.copa@gmail.com>
To: Mika Havela <mika.havela@gmail.com>
Cc: alpine <alpine-devel@lists.alpinelinux.org>
In-Reply-To: <20090803125357.B1FF337E43@smtp4-1-sn2.hy.skanova.net>
References: <20090803125357.B1FF337E43@smtp4-1-sn2.hy.skanova.net>
Content-Type: text/plain
Date: Wed, 05 Aug 2009 13:37:18 +0200
Message-Id: <1249472238.12941.117.camel@localhost.localdomain>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Mon, 2009-08-03 at 12:53 +0000, Mika Havela wrote:
> Please review and commit patch.
> 

I have a script that I use to bump versions. Its easier for me to

 abump acf-skins-0.1.7

than saving patch, copy it to the dev box, apply and test.

drawback is that you dont end up as author. sorry.

I have been thinking of having a database with packages and versions and
a web interface where users can report packages outdated and input what
version is available. similar to what Archlinux does.

Then I could have some automated stuff that tries to build all the
things users have reported. I'd still need to deal with some packages
that needs manual handling - or maybe have a bump() function in the
APKBUILD that deals with it?

Would make it alot less work to keep things up to date.

-nc




---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---