You don't need to do anything. We just move it in the buildsystem. We
can always move packages from a child repository (-channel) to the base.
If there are other issues, please contact me off-list.
Regards,
Daniel
On Tue, 2007-07-17 at 17:35 +0200, Joel Andres Granados wrote:
Daniel Riek wrote:
> On Tue, 2007-07-17 at 17:01 +0200, Joel Andres Granados wrote:
>
>>>>
>>>>
>> Question: was the fact that python-imaging got introduced to RHELClient
>> and not Server a conscious determination or
>> was it a mistake?
>> if it was a conscious determination, what are the policies that dictate
>> when and how this occurs? and where can they be found?
>>
> I think it was a side effect of the decision to move whatever required
> it to the Client but not the core Server (need to review that). There is
> no publicly available policy document on this, but in general packages
> that are pulled in by another package, move to the repository of that
> other package. It also was a mistake because I could have forseen that
> sofware wants to use it.
>
> Regards,
>
I'm the maintainer in RHEL for this package. do I need some special
considerations or do I just rebuild for 5.1?
thx.
> Daniel
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> epel-devel-list mailing list
> epel-devel-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/epel-devel-list
>
--
Daniel Riek, Product Manager Red Hat Enterprise Linux, Red Hat Inc.
E-Mail: riek(a)redhat.com,
http://www.redhat.com/
Key-FP: 3DD7 C376 C3E0 1917 9A63 6343 5A26 2C59 6C07 6F32