[Pkg-javascript-devel] Review of libv8-i18n

[Jérémy Lal]

On 01/04/2012 20:09, Jonas Smedegaard wrote:
> On 12-04-01 at 07:45pm, Jérémy Lal wrote:
>> On 01/04/2012 17:57, Jonas Smedegaard wrote:
>>> On 12-04-01 at 03:06pm, Jérémy Lal wrote:
>>>> On 31/03/2012 03:18, Jonas Smedegaard wrote:
>>>>> Did you consider using symbols file to track API/ABI changes 
>>>>> instead of simply relying on upstream version for that? Especially 
>>>>> since you really do not use upstream releases but VCS snapshots: 
>>>>> Seems unlikely to me that SONAME should be bumped exactly when 
>>>>> upstream bumps version number, rather than such changes appearing 
>>>>> at some earlier VCS commit.
>>>>
>>>> After our discussion on #debian-js : libv8-i18n doesn't have 
>>>> upstream version nor upstream soname. Choosing for upstream version
>>>> : 0~0.svn7 Choosing for soname : 0.0.0 Library version :
>>>> $(soname).0.0 Hence full lib version will be 0.0.0.0.0
>>>
>>> Well, my point about symbols file is related but different:
>>>
>>> You write in a comment in rules file that SONAME "Most likely will 
>>> change with each update."  Using symbols file it can be tracked if 
>>> in fact upstream changed the ABI or not.
>>
>> I forgot to mention :
>> http://lists.debian.org/debian-devel/2012/01/msg00671.html
>> the conclusion (faster to read) at :
>> http://www.eyrie.org/~eagle/journal/2012-02/001.html
>>
>> And it's true that the generated symbols from libv8-i18n will
>> ask for a lot of work that is not going to be useful.
>> To get the list of symbols :
>>   dpkg-gensymbols -plibv8-i18n0.0.0 -Pdebian/libv8-i18n0.0.0
> 
> I am aware of that thread.  That thread does not convince me, however, 
> that it is irrelevant to try.
> 
> Did you try, or do you consider it not worth the effort to try?

At first : not worth the effort.
I had a look in the future when revision 32 will be needed for chromium 19 :
no changes in symbols -- no apparent soname change needed. So you're right.
(and i pushed the symbols file).
But the javascript api changes, and since software using libv8-i18n will
also rely on that js interface...

Jérémy.