[poppler] track build version in output

[Josh Richardson]

Albert, yes.  We are iterating the code and builds, and converting
documents, and we want to keep track of exactly which version of the
software created which documents.

--josh

On 10/8/11 10:59 AM, "Albert Astals Cid" <aacid at kde.org> wrote:

>A Divendres, 7 d'octubre de 2011, Josh Richardson vàreu escriure:
>> Hey Popplers,
>> 
>> Wondering if anyone else would find it usefulŠ.
>> 
>> When I generate some content with pdftohtml, I'd like it to also spit
>>out
>> the build version with the content so I can keep track of which version
>>of
>> the software produced which content.  I'm guessing that this might be
>> useful in other utilities also.
>> 
>> In any case, I wanted to share my plan before I undertake:
>> 
>> 1. Modify poppler cmake system;
>> 
>>  *   add a new configure flag, INCLUDE_VERSION_IN_OUTPUT
>>  *   when set, run "git describe" on the repo when running a make
>> 
>> 2. Use perl to insert the output of "git describe" into new header file
>> that's not checked into GIT.
>> 3. Make sure that .gitignore is set for the
>> new header file; call the new header file VERSION.h
>> 4. Conditionally
>> include VERSION.h into the pdftohtml.cc build; could later be added to
>> other utils 
>> 5. Modify pdftohtml.cc to spit out the version number into the
>> output directory as a new file, "poppler-version.txt", when
>> INCLUDE_VERSION_IN_OUTPUT is configured in the poppler build.
>> 
>> Please let me know if you have any feedback.
>
>What's your use case for this? Is it because you have various builds
>running 
>internally and you want to see which one is the one causing the problems?
>
>Albert
>
>> 
>> Thanks, --josh
>_______________________________________________
>poppler mailing list
>poppler at lists.freedesktop.org
>http://lists.freedesktop.org/mailman/listinfo/poppler