On 2/20/21 12:38 PM, L A Walsh wrote:
On 2021/02/17 09:53, John Paul Adrian Glaubitz wrote:
It's rather obvious that a rolling release distribution isn't something
that corporations should use. You don't want your database server to
become offline because the daemon won't restart after an update because
the database format changed from one major version to another.
But you might want the new version of the latest CMS
to go with your website. If you wait for 2-3 years till it comes
out in leap, you've missed most of your window. Similarly with any
product, one might need a new feature from a newer product and might
even be able to _test_ the product to see if it meets one's needs. That
does not mean one wants an unstable system by replacing all packages
every day as could be the case w/TW.
Ideally we would get Leap to the point where its easy to do just this,
but with the CMS or whatever the latest core component you need you
install by yourself, either manually or maybe from a package you fork /
create on open build service. People are working on the ability to ship
multiple python / php versions with limited effort on Leap. Then you get
the best of both worlds, a stable base platform for 3-4 years but with
security updates and whatever latest production software you need, this
is what a number of SUSE Customers do.
Personally I created
cleanup) if I need the latest version of something for Leap (or SLE) I
just branch it into there and its almost 0 effort
So for TW, that'd be a different lib for each day
TW is released. i.e.
So far, I'm not seeing solutions that allow me to rebuild suse apps
from source rpm's.
Yep, most people just use obs to do this because generally its quicker
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek
SUSE Linux Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B