Naming of blitz ?

Sune Vuorela nospam at vuorela.dk
Fri Aug 24 14:31:34 BST 2007


On 2007-08-24, Mosfet <daniel.duley at verizon.net> wrote:
> Yes, I think we can change the header and library to "qimageblitz" if that 
> will solve the problem for you. 

That will definately solve the problem.

> I can also use a completely different name, but would hate to do that since 
> people are already somewhat familiar with it. Looking at Blitz++ it doesn't 
> look like it will create confusion among users since they are pretty 
> different projects, but it may be better to take care of that now.

It isn't because of user confusion, but impossibilities to have it
coinstallable that's the issue.

But a renaming will from my point of view solve everything.

/Sune


>
> On Friday 24 August 2007 3:00:50 am Sune Vuorela wrote:
>> Hi!
>>
>> I just discovered when looking into debian packaging of blitz that there
>> is something else with almost the same name - and several files being
>> the same.
>>
>> There is the libblitz pkgconfig file, there is the /usr/lib/libblitz.so
>> and such.
>>
>> The numeric part of the SONAME differs currently, blitz++ libblitz.so is
>> at .0, where kde blitz libblitz is a .4
>> But blitz++ libblitz can do soname changes and such and quickly reach
>> kde blitz.
>>
>> On sourceforge, blitz name is used by blitz++, where kde blitz has
>> qimageblitz.
>>
>> I don't know if debian is the only distribution who ends up having this
>> conflict, but I would not be surprised if other distributions was having
>> file conflicts here as well.
>>
>> I would personally dislike to make a debian specific rename of blitz, so
>> I am wondering wether kde in general sholud rename blitz to something
>> else. qimageblitz seems to have been used by the author already
>> elsewhere.
>>
>> /Sune
>
>
>





More information about the kde-core-devel mailing list