2 2

[alpine-devel] Version numbers for daily build packages

Rainer Gerhards
Details
Message ID
<CADk+mPAuaDKpyXYu_55CHpeRg50sM50XUdY9aeo04Buzuojm4A@mail.gmail.com>
Sender timestamp
1517159430
DKIM signature
missing
Download raw message
Hi all,

we (the rsyslog project) would like to build daily packages for
Alpine. I have checked APK sources, but still am a bit puzzled on how
we should name these versions. The idea is that a stable version
should always update over an equal-target-version daily build, but new
daily builds should automatically be updated.

Ex: currently 8.32.0 is our stable version, 8.33.0 is being worked on.
So far I found that we could use this scheme:

8.32.0 -> current stable
8.33g<date>, e.g. 8.33d20180128 -> daily builds
8.33.0 -> next release

apk --test tells me
8.32.0 < 8.33d2018... < 8.33.0

... but I wonder if there is a better/more standard way in Alpine of doing this.

Feedback is appreciated,
Rainer


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
William Pitcock
Details
Message ID
<CA+T2pCHEn3Xd84G2_RjwA-WTskRCZLEqVEDEa0xPiZQiOAqq9Q@mail.gmail.com>
In-Reply-To
<CADk+mPAuaDKpyXYu_55CHpeRg50sM50XUdY9aeo04Buzuojm4A@mail.gmail.com> (view parent)
Sender timestamp
1517243272
DKIM signature
missing
Download raw message
Hello,

On Sun, Jan 28, 2018 at 11:10 AM, Rainer Gerhards
<rgerhards@hq.adiscon.com> wrote:
> Hi all,
>
> we (the rsyslog project) would like to build daily packages for
> Alpine. I have checked APK sources, but still am a bit puzzled on how
> we should name these versions. The idea is that a stable version
> should always update over an equal-target-version daily build, but new
> daily builds should automatically be updated.
>
> Ex: currently 8.32.0 is our stable version, 8.33.0 is being worked on.
> So far I found that we could use this scheme:
>
> 8.32.0 -> current stable
> 8.33g<date>, e.g. 8.33d20180128 -> daily builds
> 8.33.0 -> next release
>
> apk --test tells me
> 8.32.0 < 8.33d2018... < 8.33.0
>
> ... but I wonder if there is a better/more standard way in Alpine of doing this.

The standard way would be to have 8.33_pre20180128 as the version.

William


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Rainer Gerhards
Details
Message ID
<CADk+mPB2_aveRX9uDzhN1-gZjn69MU0uSzmgw9HPfwjcSNsb8g@mail.gmail.com>
In-Reply-To
<CA+T2pCHEn3Xd84G2_RjwA-WTskRCZLEqVEDEa0xPiZQiOAqq9Q@mail.gmail.com> (view parent)
Sender timestamp
1517245175
DKIM signature
missing
Download raw message
2018-01-29 17:27 GMT+01:00 William Pitcock <nenolod@dereferenced.org>:
> Hello,
>
> On Sun, Jan 28, 2018 at 11:10 AM, Rainer Gerhards
> <rgerhards@hq.adiscon.com> wrote:
>> Hi all,
>>
>> we (the rsyslog project) would like to build daily packages for
>> Alpine. I have checked APK sources, but still am a bit puzzled on how
>> we should name these versions. The idea is that a stable version
>> should always update over an equal-target-version daily build, but new
>> daily builds should automatically be updated.
>>
>> Ex: currently 8.32.0 is our stable version, 8.33.0 is being worked on.
>> So far I found that we could use this scheme:
>>
>> 8.32.0 -> current stable
>> 8.33g<date>, e.g. 8.33d20180128 -> daily builds
>> 8.33.0 -> next release
>>
>> apk --test tells me
>> 8.32.0 < 8.33d2018... < 8.33.0
>>
>> ... but I wonder if there is a better/more standard way in Alpine of doing this.
>
> The standard way would be to have 8.33_pre20180128 as the version.

Thanks, that was very useful. I didn't find that convention anywhere.
I have now changed the version to that format.

Rainer


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---