Reinstantiation of the KDK

[Steven Suson]

Greetings Ralf,

    I had failed to consider this new level of integration with KDE as a whole, in my reconsideration of
the KDK. My bad. I like the approach that you mention about care in packaging. By careful use of the
dependency mechanisms of whichever type of packaging, you could assure all the pieces are present. For
example, the kdevelop package is dependent on perhaps the kdesdk, which either includes (kde stuff), or
is itself dependent on external packages (e.g. htdig), and thus all falls into place.

Thanks for your time,
Steven Suson
"Keep the faith."

Ralf Nolden wrote:

> Berndt Josef Wulf wrote:
> >
> > Steven Suson wrote
> > > Greetings all,
> > >
> > >     Having done a bit of driving this last weekend, and while doing so,
> > > some software design, etc., I was thinking about the many emails on this
> > > list having to do with installation issues, compatibility issues with
> > > various packages used by kdevelop, and things along these same lines. It
> > > seemed to me that many of these were addressed previously with the KDK.
> > >
> > >     So, I just wanted to throw this out to the list, to see what
> > > everyone else thought. In terms of getting the great kdevelop IDE into
> > > not only more hands, but also into more widely varied hands, would
> > > reinstantiation of the KDK (say, a 1.3 and 1.4 version for KDE1 and
> > > KDE2, respectively) give us more bang for our buck? I'm very interested
> > > in what everyone thinks.
> >
> > The KDK package was a great way of getting a complete IDE without
> > worrying about the details of its installation, especially for
> > newbies. I'm in support for a call to re-instantiate the KDK package
> > and willing to help.
> >
> > cheerio Berndt
>
> Ok, my vote is that as KDevelop ships now with KDE releases what I did
> last time was to make sure kbabel and kdoc gets installed and shipped.
> Maybe putting Cervisia into the kdevelop branch as well would be an
> option, about the C reference I guess you all know that Ingo Zevenbergen
> is rewriting a new one that ships with kdevelop then directly. But a KDK
> like we used to have doesn't make much sense as it would require
> decoupling the kdevelop releases from KDE again which is not what the
> goal is. Please think about ideas what is needed and how to get stuff
> into either kdesdk or kdevelop tags in CVS so that it is directly
> available at packaging time. The packagers of the distributions will
> thank you *a lot* if that is complete. I've been talking e.g. to Klaas
> Freitag at SuSE to get a proper kdevelop package and the result is on
> suse 7.1 that it works perfect with just selecting kdevelop in the
> xdevel section and all dependencies are fullfilled. As far as graphic
> apps are concerned or other mime-types I could add desktop files for
> designer and linguist but the rest is done by KRun so it's up to the
> user to decide which app to use. Maybe someone could volunteer for the
> Real file viewer to rewrite that in a more konqueror style avoiding the
> reload on changes, adding menu entries for "open with" and the default
> apps like konqueror has ?
>
> Ralf
> --
> Finally, even I have to admit that being myself was the best thing
> that ever could have happened to me. - Le Grand Charmeur
>
> **********************************
> Ralf Nolden
>
> The KDevelop Project
> http://www.kdevelop.org
>
> nolden at kde.org
> rnolden at kdevelop.org
> **********************************
>
> -
> to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
> unsubscribe »your-email-address«


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«