On Wed, 16 Jul 2014, Stephan Wiesand wrote:

> But I think SL_no_colorls is flawed. Marc, did you never have the 
> problem that dircolors returned after a coreutils update? Moving the 
> files out of the way IMO should be done in "%triggerin -- coreutils" 
> rather than "%post" to prevent that and to make the results independent 
> of the installation order...

Please consider the following advice from Red Hat:

     https://access.redhat.com/articles/rhel-abi-compatibility

     5. Package applications using the RPM mechanism. RPM provides a
        software-packaging mechanism that includes detailed specification
        of application dependencies. When creating RPMs, the following
        should be kept in mind:

        (a) Avoid using RPM triggers whenever possible.

        (b) Explicitly state all required runtime and build dependencies
            using the appropriate RPM syntax.

        (c) Do not modify, replace, or recompile files managed by Red
            Hat-provided RPM packages. Doing so may lead to unpredictable
            behavior.

        (d) When considering dependencies, do not assume that all possible
            packages will be installed on every Red Hat Enterprise Linux
            system. The default installed packages may change between major
            releases, between product variants of the same version, and on
            a customer’s system. For instance, the Workstation product will
            have a different installed package set than the Server product.

        Rarely, and due to extenuating circumstances, packages might be
        removed  between minor releases but Red Hat will provide
        notification if this occurs.

And these guidelines cover Scientific Linux equally.

-- 
-- dag wieers, [log in to unmask], http://dag.wieers.com/
-- dagit linux solutions, [log in to unmask], http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]