On Monday 31 of March 2014 01:26:51 Timothy Pearson wrote:
> > On Monday 31 of March 2014 00:43:33 Timothy Pearson wrote:
> >> Cross-post from the users list:
> >>
> >> When TDE crashes and Dr. Konqi appears...
> >>
> >> ...please click "Report Crash" instead of "Close".  TDE now has a
> >> powerful
> >> automated crash reporting system that will let you submit a crash report
> >> with as little as three mouse clicks--no personal information, logins,
> >> or
> >> version descriptions are required.  Of course we would appreciate a
> >> problem description and possibly a contact Email address, but if you
> >> don't
> >> have time or just don't want to give that information out you can still
> >> submit the crash report for analysis and repair.
> >>
> >> Developers: Automated crash reports are visible at
> >> https://crashreport.trinitydesktop.org.  Click on the crash ID for a
> >> detailed report.  Let me know what you think, and if you have any
> >> suggestions please let me know!
> >>
> >> Tim
> >
> > I miss one important piece of information:
> > What is necessary to do when building packages?
> > It is necessary to prepare the file with scm informations?
> > Is it documented somewhere?
> >
> > --
> > Slavek
>
> Hi Slavek,
>
> It is not documented anywhere as this feature is intended only for
> automated builds; here is a brief description so that you can add support
> to your builds:
>
> TDE will look for the SCM information on the first line of two hidden
> (dot) files in the root of the build source directory:
>
> ${CMAKE_SOURCE_DIR}/.tdescmmodule
> the name of the GIT module in which the current sources are stored.
> For example, "tdelibs" or "applications/amarok" (without the quotes)
>
> ${CMAKE_SOURCE_DIR}/.tdescmrevision
> The branch and long hash of the module sources being built, separated with
> a dash
> If the branch is empty, master is assumed.
> For example, "-f5b2a9a7b203e89c1553ffa9a8371bac32f21aa3" or
> "master-f5b2a9a7b203e89c1553ffa9a8371bac32f21aa3" (without the quotes)
>
> Tim
>

Thank you for the informations. I added the automatic creation of SCM metadata 
into the script create_tarball - see commit c5010d96.

-- 
Slavek