pidgin.openq: 6fc65db6: 2008.10.07 - lonicerae <lonicerae(at)gma...

SHiNE csyfek at gmail.com
Mon Nov 3 23:11:08 EST 2008


1, we do NOT want to shipping openq separately from libpurple, you
misunderstand our purpose.
2, just as Phil said, this enable us to know which revision testers is
using, and help them make bug report more easily.
3, as you know, there is no monotone tutorial in Chinese, so i'm
trying my best to write one for developers who are not good at English
but good at programming. now, ccpaging is using monotone too. is it
not a good news to enable more developers to join pidgin project and
openq project etc.?
4, this script wil stay there till we migrate from mecurial to monotone.
5, the compile errors has been solved since
52b673726ba47e370199600825aae32d47e76d6c.  flos and i tested in msys
on Windows and Gentoo and Debian. running 'make -f Makefile.mingw' in
msys and 'autogen.sh' in those Linux distros all got through.

Thanks all guys,

SHiNE
2008/11/3 Phil Hannent <phil at hannent.co.uk>:
> Richard Laager wrote:
>> On Wed, 2008-10-22 at 12:11 -0400, csyfek at gmail.com wrote:
>>> --- libpurple/protocols/qq/Makefile.am       7b58ebc44b1131d5c8d7ee3b6e731725576d7a81
>>> +++ libpurple/protocols/qq/Makefile.am       a1dd9472927a1f3089b9ed4ecc3c47c6cfe0c584
>>> @@ -59,6 +59,11 @@ libqq_la_LDFLAGS = -module -avoid-versio
>>>
>>>  libqq_la_LDFLAGS = -module -avoid-version
>>>
>>> +CURRENT_REVISION=$(shell \
>>> +             awk 'BEGIN {"grep node .hg_archival.txt" | getline rev; \
>>> +             rev=substr(rev,7,6); \
>>> +             print rev}')
>>> +
>>
>> This breaks the build, because I don't have a .hg_archival.txt file.
>> Also, we use Monotone, not Mercurial, so I'm not sure what this is doing
>> there at all. Please fix this immediately.
> For a Qt based project I am working on at work I implemented:
>
> exists(_MTN):DEFINES += BUILDREVISION=\\\"$$system(mtn automate
> get_base_revision_id)\\\"
> else:DEFINES += BUILDREVISION=\\\"NOT BUILT FROM SOURCE REPOSITORY\\\"
>
> This enabled me to know exactly which build a tester was using.  It would be
> cool if Pidgin and libpurple did a similar thing and displayed the version in
> the about box.  This would help with verifying if people are building their own
> and if they have a miss-match libpurple and pidgin.
>
> Regards
> Phil Hannent
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/devel
>
>



-- 
~~-~~-~~-~~-~~-~~-~~-~~-~~-~~-~~
   First the truth, then the freedom!
~~-~~-~~-~~-~~-~~-~~-~~-~~-~~-~~




More information about the Devel mailing list