~sircmpwn/alpine-devel (mirror)

5 5

have next stable (e.g. v3.15) as transitional symlink to edge in the repository?

Details
Message ID
<271ced6b60f44bb4ba2718e811337a70@vodafonemail.de>
DKIM signature
pass
Download raw message
Hi,
sometimes I'd wish it could be possible to let a system only temporarily follow
edge development, but stay on the next stable release when it gets out.

Could you enable this (simply) within some release script, by having it create
an additional symlink for the next stable release (e.g. /v3.15) in the 
repositories that would poindt to /edge? (In addition to creating/replacing
he new latest-stable and vX.Y release locations.)

Kind regards
 -Al
Francesco Colista
Details
Message ID
<a2e38a73194692e25f0702dc8f9c32bb@alpinelinux.org>
In-Reply-To
<271ced6b60f44bb4ba2718e811337a70@vodafonemail.de> (view parent)
DKIM signature
pass
Download raw message
16 luglio 2021 17:20, alpine@vodafonemail.de wrote:

> Hi,
> sometimes I'd wish it could be possible to let a system only temporarily follow
> edge development, but stay on the next stable release when it gets out.

> Could you enable this (simply) within some release script, by having it create
> an additional symlink for the next stable release (e.g. /v3.15) in the 
> repositories that would poindt to /edge? (In addition to creating/replacing
> he new latest-stable and vX.Y release locations.)

This "simply" modification put a burden on the infrastructure side.
Considered the minimum benefit of this, compared with the difficulties related to handling this "simply" modification, I don't think is worthy at all.


.: Francesco Colista
.: Alpine Linux Core Dev Team
Nathan Angelacos
Details
Message ID
<bfd8e62b2d46db6db97063c58564cc2b0b6eeb1c.camel@alpinelinux.org>
In-Reply-To
<271ced6b60f44bb4ba2718e811337a70@vodafonemail.de> (view parent)
DKIM signature
pass
Download raw message
On Fri, 2021-07-16 at 17:20 +0200, alpine@vodafonemail.de wrote:
> 
> Hi,
> sometimes I'd wish it could be possible to let a system only
> temporarily follow
> edge development, but stay on the next stable release when it gets
> out.
> 


Hey, that's an interesting question.  You want to follow edge, until
the next release is available.  Which is contradictory.

>From my experience I have hosts on edge, which are always broken
somehow.... (that's the point of edge!) and hosts that are still on 3.7
because I forgot to update them.


Are you asking to have a script to update the MOTD to say "version X is
now available... to upgrade, run apk -U (super)-upgrade?"  Something
like Unbuntu does - tells us when there is a new release available?

I'm just asking.  I think its an interesting question.
Nathan Angelacos
Details
Message ID
<0e9e48a91a11c2e622aa747380ccd705845ad28b.camel@angelacos.net>
In-Reply-To
<a2e38a73194692e25f0702dc8f9c32bb@alpinelinux.org> (view parent)
DKIM signature
missing
Download raw message
On Fri, 2021-07-16 at 16:48 +0000, Francesco Colista wrote:
> 
> 
> This "simply" modification put a burden on the infrastructure side.
> Considered the minimum benefit of this, compared with the
> difficulties related to handling this "simply" modification, I don't
> think is worthy at all.
> 

Totally agree... but ubuntu solved this by saying "Hey.... Version X.YY
is now available."    The switch to systemd was painful.  But it was my
choice.   I wonder if it is possible to notify on login.  Not force,
just notify.
Details
Message ID
<35bd34e-1481-487-40ad-428a25ad4833@dereferenced.org>
In-Reply-To
<271ced6b60f44bb4ba2718e811337a70@vodafonemail.de> (view parent)
DKIM signature
pass
Download raw message
Hello,

On Fri, 16 Jul 2021, alpine@vodafonemail.de wrote:

>
> Hi,
> sometimes I'd wish it could be possible to let a system only temporarily follow
> edge development, but stay on the next stable release when it gets out.

To be clear: the contents of the Alpine edge repository *never* become a 
release.  Once in a while, we take the Alpine edge repository, and use 
that as the basis of a distro-wide rebuild to create a new release branch.

Mixing edge and the next release once it is branched is not recommended, 
in the same way that mixing edge and the current/older releases is not 
recommended.

> Could you enable this (simply) within some release script, by having it create
> an additional symlink for the next stable release (e.g. /v3.15) in the
> repositories that would poindt to /edge? (In addition to creating/replacing
> he new latest-stable and vX.Y release locations.)

No, because it will create problems: users will follow v3.15 and get edge, 
then will not be properly upgraded to v3.15 release when it occurs, unless 
they explicitly use `apk upgrade --available`.

Ariadne
opal hart
Details
Message ID
<20210726063323.32694163@mahin.internal>
In-Reply-To
<bfd8e62b2d46db6db97063c58564cc2b0b6eeb1c.camel@alpinelinux.org> (view parent)
DKIM signature
pass
Download raw message
On Fri, 16 Jul 2021 12:57:27 -0400
Nathan Angelacos <nangel@alpinelinux.org> wrote:

> Hey, that's an interesting question.  You want to follow edge, until
> the next release is available.  Which is contradictory.

I think of it as a pre-release or RC of the next-coming version, for
packages someone wants from an upcoming stable release. However, I've
solved the issue of needing certain package versions by adding edge asa
tagged repository and then doing something like `apk add foo@edge`.

> >From my experience I have hosts on edge, which are always broken  
> somehow.... (that's the point of edge!) and hosts that are still on 3.7
> because I forgot to update them.

latest-stable is an alias that points to exactly what it says. You can
use that in your repositories config.

-- 
wowaname <https://wowana.me/pgp.xht>
Reply to thread Export thread (mbox)