Message-ID: <56393690-ff91-30fa-6324-b5e728e90184@gmail.com>
Date: Sat, 31 Dec 2022 12:04:13 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
To: ~alpine/devel@lists.alpinelinux.org
Reply-To: vkrishn4@gmail.com
Content-Language: en-US
From: "V.Krishn" <vkrishn4@gmail.com>
Subject: suggesting feature, splitting pkgs repositories
Organization: Insteps.net
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi!

Going to put pros/cons last. This feature suggest is desirable
because sometimes regressions or changed features in apps causes
pkgs to stop working.
This is not a rollback kind setup, but trying to preserve
pkgs that were released in versioned, and does not apply to edge.
There are some more ways of doing it, eg. using layering or similar.

3.16    - the active working directory,
           it gets renamed and empty dir recreated
           (if this breaks something, symlinks to pkgs can be added back)
3.16.0  - first full release
3.16.1  - dir with only updated pkgs and relevant APKINDEX.tar.gz
           (only full pointy cuts, based on aports tag,
            and not intermediate updates)
3.16.2  - ... so on

/etc/apk/repositories urls
https://dl-cdn.alpinelinux.org/alpine/v3.16.0/main/
# below links gets added manually or apk suggests availability
#  in `apk update` or `apk checkupdates`
https://dl-cdn.alpinelinux.org/alpine/v3.16.1/main/
https://dl-cdn.alpinelinux.org/alpine/v3.16.2/main/
# ...

Pros:
1. Preserves versioned released pkgs.
2. Some regressions could be fixed.
Cons:
1. Will lessen the edgy feel of alpine.
2. Mirror size increases.
3. Not fully backcompat, and will require changes
    to current automated alpine setups.

-- 
Regards,
V.Krishn