On Thu, May 23, 2019 at 10:43 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
Really? Because I was told the other day that Orion (which was part of OPS) is not going to be part of the new delivery.
I take it you are responding to
The document says that all features are now available via RPM packages.
I read over Justin's link, and I didn't see anything that says that.
It's possible I missed it, or I don't understand IBMspeak, but I don't
think it's in there.
What the document does say, in the very first line, all by itself, is
All future open source packages are delivered via RPM only.
As far as I can tell, the document doesn't even say that ANY of the
existing 5733-OPS software is or will be provided as RPMs.
Now, it so happens that a lot of the *functionality* is duplicated or
superseded by RPMs. For example, there are old Node.js and Python
versions in 5733-OPS. Those old ones are NOT strictly provided as RPMs
today, nor will they ever be. But in most cases, you can use a
superseding RPM (for example, most users of Python 3.4 can migrate
fairly straightforwardly to Python 3.6). I fully expect there are some
shops that have very version-sensitive dependencies (witness Rob's
continual Java-related struggles) and those shops may need to stay on
5733-OPS long past end of support.
As an Amazon Associate we earn from qualifying purchases.