Message-ID: <3f660cec-5df1-486f-9165-04656e1d6f75@gmail.com>
Date: Mon, 5 Oct 2026 18:41:56 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Reply-To: vkrishn4@gmail.com
Subject: Re: how to maintain a set of local packages, probably a feature
 request
To: Hugo Osvaldo Barrera <hugo@whynothugo.nl>
References: <82a82852-43fc-4336-9037-4ba8fd7241b7@gmail.com>
 <376650b2-93e6-4470-b5f8-8b7d87e7d9c2@app.fastmail.com>
Content-Language: en-US
Cc: ~alpine/devel@lists.alpinelinux.org
From: "V.Krishn" <vkrishn4@gmail.com>
Organization: Insteps.net
In-Reply-To: <376650b2-93e6-4470-b5f8-8b7d87e7d9c2@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 10/5/26 17:35, Hugo Osvaldo Barrera wrote:
> 
> 
> On Mon, 5 Oct 2026, at 19:29, V.Krishn wrote:
>> Hi,
>>
>> I am planing to build/maintain a small set of packages locally,
>> (after some experimental changes),
>> below is a versioning method I was thinking to do,
>>
>> For packages that are already in aports,
>> a. have same version as in aports, so as to keep in track/update with
>> upstream alpine-aports version.
>> b. add some sort to policy marker in version, eg. package
>>      abc-xyz-1.2.3-r0-vkr
>>
>> Entry in APKBUILD would look like:
>> -------------
>> pkgname=abc-xyz
>> pkgver=1.2.3
>> pkgrel=0
>> brand=vkr
>> -------------
> 
> abuild has no awareness of this "brand" field. It won't
> be included in the package, nor in the index. apk is
> oblivious to this value being set here.
> 

I think I would do a feature request for it in gitlab, but wait for some 
comments to reason out its usability.

-- 
Regards,
V.Krishn