[WBEL-devel] Re: [WBEL-users] Odd window drag behaviour

[John Morris]

It has a patch for RHEL version of metacity package - I have it
locally applied until it gets its way into the official update.

Ok, this one bugs me enough I'm wondering if it justifies pushing up a
patched version of metacity instead of waiting for RedHat to get around to
it in U3. I know I'll be adding this patch to my own copies, but should
it go into the mainline? It would mark a departure from tracking RH
exactly and that worries me.

[William Hooper]

Post by John Morris

It has a patch for RHEL version of metacity package - I have it
locally applied until it gets its way into the official update.

Ok, this one bugs me enough I'm wondering if it justifies pushing up a
patched version of metacity instead of waiting for RedHat to get around to
it in U3. I know I'll be adding this patch to my own copies, but should
it go into the mainline? It would mark a departure from tracking RH
exactly and that worries me.

Sounds like a good candidate for that "WBEL Extras" channel that you created.


--
William Hooper

[John Morris]

Post by William Hooper
Sounds like a good candidate for that "WBEL Extras" channel that you created.

Actually that one is destined to get the RH doc packages, clustering,
eclipse, GFS and other packages hatched by RH but not appearing in the
RHEL SRPM collection.

Might need to have a channel for grey area patches. Need to define its
focus narrow enough that it can't grow much. Probably limit to patched
versions of packages already shipping. Existing 3rd party repos for
RHEL/WBEL packages should be the proper venue for most packages that add
functionality.

[James Knowles]

Post by John Morris
Might need to have a channel for grey area patches. Need to define its
focus narrow enough that it can't grow much. Probably limit to patched
versions of packages already shipping.

I think this is a great idea for these "highly annoying" or otherwise
pesky mainline bugs as long as the "grey area" packages get removed when
the official fixes come along. I don't know anything about how the
channels &c. operate, so I don't know if it's economical or otherwise
can be done automatically within the scope of the up2date/yum programs.

If its scope is narrow enough, there aught to be no more than a handful
of these "grey area" patched packages, no?

[James Knowles]

keep all the fixed packages clearly separated, and be
ready to restore the original set

I second this. I've played the non-standard RPM game enough to be burned
to a blackened crisp several times.