[Kde-imaging] Reg KIPI

[Vardhman Jain]

On 3/29/06, Tom Albers <tomalbers at kde.nl> wrote:
>
> Op Tuesday 28 March 2006 17:56, schreef Vardhman Jain:
> Yep. To be honest, I dont think anyone will do the necessary work on
> libkipi
> for you. If you need it, you need to make it yourself. I don't think
> anyone
> with knowledge has time or motivation (to prevent a misunderstanding: I
> know
> less about libkipi then you do).


Yes I am not denying the responsibility of changing the libkipi stuff
myself, but as a developer with relatively less experience I wanted to ask
in the list of that kind of extention (adding a function or two in the
interface) is okay. I am specially concerned about it breaking any
compatibility with other apps. I would probably be testing it with the
Digikam interface only.

Please let me know specifically as to whether adding some code in
libkipi/libkipi/imageinfoshared.h libkipi/libkipi/imageinfoshared.cpp in the
class definition/declaration is okay for everyone or not?

> Also Can we have a more regular release
> > schedule for kipi-plugins ? If its too difficult to coordinate why not
> > allow the Digikam developers to take the complete responsbility. I am
> not
> > trying to start a flame war here, I just want to express my concern over
> > the issue.
>
> The release script is in svn, anyone can run it and make a tarball. There
> is a
> kipi sf page where you can get access to to upload it. Again, this is
> something _you_ can do.
>
> remark 1
> The digikam team has a new packager, maybe someone should contact him and
> ask
> to do it for kipi as well, I think he will enjoy it.
>
> remark 2
> in the digikam repository there are packaging instructions, maybe they are
> usefull to read.
>
> > As a kipi-developer, I don't see my plugin being available to the user
> > easily. (First they have to seperately install this libkipi etc stuff
> and
> > then the updated version can only be obtained from the SVN). With so
> much
> > development going on in various kipi-plugins we should atleast ensure as
> > frequent issues of kipi as we have for digikam and digikam image
> plugins.
> > This is not to overshadow the other projects which support kipi but only
> to
> > enhance the kipi-plugins availability to users.
>
> I think it would be best to package it now (as in asap) as final version
> (unless there are grave bugs), so that is behind us and start with a clean
> sheet.
>
> I'm available for questions about the packaging.
>
> Toma
>
I am going to spend some time reading the scripts and see if I can help
myself.

Vardhman
--
Blogs: http://vardhman.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-imaging/attachments/20060329/6025c15e/attachment.html