Aggregation upstream projects are BAD (kdesdk for example)

[Jon Ciesla]

> seth vidal wrote:
>> On Sat, 2007-09-08 at 15:12 +0200, Hans de Goede wrote:
>>> Hi All,
>>>
>>> A college of mine wanted to use umbrello in our Universities labs,
>>> since the
>>> Linux install there are Fedora he asked me about umbrello for Fedora.
>>>
>>> Since I could NOT find it, I packaged it, see:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=283471
>>>
>>> But then I got a comment to the review it was already in Fedora in
>>> kdesdk. But
>>> then why on earth doesn't kdesdk have a Provides umbrello so that yum
>>> install
>>> umbrello works? Or even better an umbrello sub-package?
>>>
>>
>> File a bug with the maintainer of kdesdk and ask them add provides for
>> each of the programs that it includes.
>>
>> Do it for all of the items you think is important. I think that's a fair
>> thing to do.
>>
>
> I forgot to say in my mail I already did that, see:
> https://bugzilla.redhat.com/show_bug.cgi?id=283521
>
> But that still doesn't solve the version interlocking of completely
> unrelated
> packages.

I agree (though I will start the umbrello review, examining all issues but
the kdesdk one, which appear to be slogging out here :) ), but if kdesdk
inclused umbrello, even if it does so along with 45 grintwillion other
applications etc, until they either split out umbrello or include
Provides, would not the umbrello package Conflict, and isn't that a No-No?

I'm all for having it sepearate, don't misunderstand, but don't our
efforts depend somewhat on the actions of the kdesdk maintainer?

-Jon

> Regards,
>
> Hans
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>


-- 
novus ordo absurdum