On 7/12/07, Johnny Hughes <mailing-lists(a)hughesjr.com> wrote:
Konstantin Ryabitsev wrote:
> So, here's a fun situation:
>
>
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246444
>
> In brief:
>
> * python-imaging in EPEL conflicts with python-imaging in RHEL-5Client
> * upstream (RHEL5) requests to remove python-imaging because EPEL is
> not supposed to override upstream
> * removing python-imaging will break dependencies in RHEL-5Server
>
> How do we deal with the fact that there is RHEL-5Server and
> RHEL-5Client and that they have different sets of packages?
>
How about just tell them to use yum-priorities? Then, the server guys
do not get it and the client guys do.
You can also have another repo that is Client-only ... and the only
thing that goes there are deps that do not exist in rhel-server???
You are also going to have things that are in 5 and not 4 (and vice versa).
5 vs 4 is handled. The policy is to provide what is NOT provided by
upstream (RHEL in this case). So if RHEL 4 doesn't include something,
EPEL can. If RHEL 5 includes it, EPEL will not.
The client vs server issues on RHEL 5 have been brought up before, but
still with no good solution offered...thus far.
stahnma
You will need to handle all these somehow.
_______________________________________________
epel-devel-list mailing list
epel-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list