[scl.org] Is software collections appropriate for making a self-contained software archive?

[Shawn J. Goff]

On 05/21/2014 03:41 PM, Jim Perrin wrote:
>
> On 05/21/2014 02:30 PM, Shawn J. Goff wrote:
>> I have to install some software in an enterprise environment where we
>> are limited to installing in a specific directory in /opt. Additionlly,
>> we can't use yum or rpm to install it - it has to be simply built or
>> extracted right into the directory.
>
> How would you go about installing updates or security patches without
> rpm or yum? Not using rpm for an rpm based distribution seems highly
> counter-productive.

Rebuild and re-install, unfortunately.

Agreed about counter-productivity. This is not my enterprise; I have no
control over this monster.


>
>
>> Software collections seems to allow building an RPM that installs a
>> package and all its dependencies in such a directory. I'm thinking I can
>> make such a package, install it on a dev system, tar up the install
>> directory, then untar it on the production system. Should I expect that
>> to work?
>>
> It may, but you'd also have to ensure that any dependencies are also
> installed, and these may not always end up in /opt. Some scl packages
> (especially services) also drop files outside /opt as well.
>

Since I'm building the collections, I'm expecting to have control over that.