Kornel Benko <kor...@lyx.org> writes:

| Am Sonntag, 11. März 2012 um 20:41:12, schrieb Lars Gullik Bjønnes 
<lar...@gullik.org>
>> Kornel Benko <kor...@lyx.org> writes:
>> 
>> | Am Sonntag, 11. März 2012 um 19:53:02, schrieb Lars Gullik Bjønnes 
>> <lar...@gullik.org>
>> >> | +#message(STATUS "gitversion = ${LYX_GITVERSION}")
>> >> | +if(LYX_GITVERSION)
>> >> | +     EXECUTE_PROCESS(COMMAND ${LYX_GITVERSION} "describe" 
>> >> WORKING_DIRECTORY "${TOP_SRC_DIR}" OUTPUT_VARIABLE LYX_PACKAGE_RELEASE 
>> >> OUTPUT_STRIP_TRAILING_WHITESPACE)
>> >> | +     if (LYX_PACKAGE_RELEASE MATCHES "^2\\.0\\.0\\-\([0-9]+\)\\-.*$")
>> >> | +       # We will add offset of 40000 to get appropriate value to
>> >> | +       # previous svn.
>> >> | +       # We use this value than also to set the package-patch-value
>> >> | +       MATH(EXPR LYX_REVISION_VERSION "(${CMAKE_MATCH_1}+40000)")
>> >> 
>> >>           This looks like something specific for 2.0.x, is that right?
>> >> 
>> >
>> | No, I am parsing only the `git describe` in its current output.
>> >
>> >> And if not in 2.0.x you just use the output from git describe?
>> >
>> | No, in that case nothing is done. The value will be '1', e.g. 
>> lyx-2.1.1-Linux.deb instead of lyx-2.1.41397-Linux.deb
>> >
>> >> This when running in some non VC context? (tarfile etc)?
>> >
>> | Sort of. Package context.
>> 
>> Ok, I think I ended up being more confused. The official numbers are
>> triplets, you are not changing them are you?
>
| Its package naming and handling only. LyX itself identifies as 2.1.0svn.

Right, but isn't "2.1.0svn" somehow part of the package name?

Where can I see a list of these package names, so that I perhaps can
understand how this works?

-- 
   Lgb

Reply via email to