~alpine/devel

1

suggesting feature, splitting pkgs repositories

Details
Message ID
<56393690-ff91-30fa-6324-b5e728e90184@gmail.com>
DKIM signature
missing
Download raw message
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
Details
Message ID
<5ecbb117-5dda-fcf1-7130-4206253b7c94@gmail.com>
In-Reply-To
<56393690-ff91-30fa-6324-b5e728e90184@gmail.com> (view parent)
DKIM signature
missing
Download raw message
On 12/31/22 12:04, V.Krishn wrote:
> 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.

3. Once mirrors syncs fully any pointy release eg. v3.16.1, it would 
mean this repo will not change in future, therefore not being in 
constant flux. (i.e minor issues arising out of not syncing mirrors, 
when updates happen).

> 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
Reply to thread Export thread (mbox)