[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    Re: [Kde-bindings] kdebindings in KDE trunk: how to move forward
From:       Richard Dale <rdale () foton ! es>
Date:       2006-11-20 17:29:14
Message-ID: 200611201729.14319.rdale () foton ! es
[Download RAW message or body]

On Friday 17 November 2006 21:40, Caleb Tennis wrote:
> I'd like to get the discussion started on how we want to structure the
> kdebindings module as we move forward.  I'd like to propose that we get rid
> of the toplevel build stuff like it is now and subdivide each of the
> sections into language categories:
>
> kdebindings/ruby
> kdebindings/java
> kdebindings/perl
>
> etc
>
> that way, we can package the bindings project up per language instead of
> packaging them up as a whole group and having to do global checks for the
> presence of interpreters, libraries, and headers.
>
> Perhaps smoke, kalpytus, and ? can all go into kdebindings/utilities
>
> Any thoughts?
Sounds good to me, but I don't really have much opinion either way. What about 
lightweight scripting projects for dbus like we had for dcop - should they go 
in a separate 'dbus-scriptiing' directory or under kdebindings/ruby, 
kdebindings/python etc?

-- Richard
_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings
[prev in list] [next in list] [prev in thread] [next in thread]