You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Looking for rationale why versioned OSMH sources aren't available for OSMH groups

in Linux 5 comments

Summary:

I have multiple customers who would love versioned OSMH sources that can be used with OSMH groups. The lifecycle environment approach isn't feasible because we don't have a specific set of installed packages—instead we are looking for only a controlled collection of package versions to be available to all hosts in a OSMH group. We are using unversioned non-updating custom sources now (that are simply a collection of OCI-provided sources) but having the versioned source lock capability would be a great addition!

Content (please ensure you mask any confidential information):

We have multiple unrelated servers running a consistent major OS release (i.e. OEL8) and we'd like to have a locked set of packages and versions available to all of these unrelated servers. We would prefer the guarantee of a versioned OSMH source to give the customer peace of mind that the versions remain unchanged until the source is swapped out on a schedule (for a newer assembled versions of the same packages but with later versions).

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!