A humble packager's request: Retire kdeaddons.

[Dominique Devriese]

David Faure writes:

> On Tuesday 17 February 2004 10:39, Chris Cheney wrote:
>> On Thu, Feb 12, 2004 at 11:53:23AM +0100, David Faure wrote:
>> > kdesdk isn't about developing FOR kde (only), it's about
>> > developing WITH kde.  IMHO it would be a good place for
>> > unsermake.
>> >
>> > > And kdenonbeta, well, is a mess.  It's an annoyance to keep
>> > > something that's mature there just because there's no better
>> > > location.
>> > Yes - and it's not packaged so it requires using CVS (whereas
>> > kdesdk is available everywhere, so having unsermake there would
>> > make it easier for people to use it when compiling e.g. kde
>> > tarballs).
>>
>> Having unsermake in kdesdk will cause a circular dependency if
>> someone wants to build kde with it, as long as kde is written to
>> use autotools this will be fine. But its something to keep in mind.

> Wrong: unsermake itself doesn't need to be built, it's all python,
> you only need to export a VAR to it. So you need kdesdk checked out,
> but that's all. No circular dependency.

And how would this be packaged ?  kdelibs would have a build-depends
on kdesdk, which has a build-depends on kdelibs ?

cheers
domi