DKIM2-Signature: i=1; m=1; t=1791221750; d=whynothugo.nl;
	mf=PGh1Z29Ad2h5bm90aHVnby5ubD4=;
	rt=PH5hbHBpbmUvZGV2ZWxAbGlzdHMuYWxwaW5lbGludXgub3JnPg==;
	s=fm3:rsa-sha256:x83KDCuaEikQ2pjLkDUyw7JiRN9pwybWJIx6awM3o+w0qEG
	MeGUJavhyRGrW/mhQJWYWnaTWNN0mbxQhZNffhnGOUDQ/q92tNlfiilvzc6nQXgV
	Mi5FRN4miJQptBLKZqXEM+a0Fjnq/GMBs5rkRrPSdjHruoKhot2DdwyulRKh36WY
	aSJSuvkPsi7JF2v1ssPdaAYNNnkYjclV4rtrnKhsVzB3JMOYESBuGuIARe3cnLGH
	M/HyGTsnWowRILXHG3EW6oS52CA0zF2utbUZHZjHJxNB31L6e+cy8QJjL0ofPMNN
	69Z6gKX7hnggEW1CbO8WzVGqaSGNMPSnKKLkF3A==;
Message-Instance: m=1; h=sha256:f/Ps+z8ZOD3Telo2YD+lNgjm4jX6SniLy0CeJ/cdfzc=:Cf5A2ty8XFGIzZjQnOzeBinYVk+KCq5+ACSZA4Kw/Rc=;
Feedback-ID: ib8c04050:Fastmail
MIME-Version: 1.0
Date: Mon, 05 Oct 2026 19:35:28 +0200
From: "Hugo Osvaldo Barrera" <hugo@whynothugo.nl>
To: ~alpine/devel@lists.alpinelinux.org
Message-Id: <376650b2-93e6-4470-b5f8-8b7d87e7d9c2@app.fastmail.com>
In-Reply-To: <82a82852-43fc-4336-9037-4ba8fd7241b7@gmail.com>
References: <82a82852-43fc-4336-9037-4ba8fd7241b7@gmail.com>
Subject: Re: how to maintain a set of local packages, probably a feature request
Content-Type: text/plain
Content-Transfer-Encoding: 7bit



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.

-- 
Hugo