KDE Applications Versioning

Christoph Cullmann cullmann at absint.com
Sun Jul 5 12:11:30 UTC 2015


Hi,

here you go:

http://commits.kde.org/kate/28eb1504df1762e7e96cc5dfe4a983360dc560f8

If you have boilerplate like:

http://quickgit.kde.org/?p=kate.git&a=blobdiff&h=77c35ae71216a6f9e04693f0db7c63b7f793d287&hp=073d6d9cae3c1f51941ed44517978ca16c04da41&hb=f99377b27ac9c9ba5cd92c6e91036ecf9403ca99&f=CMakeLists.txt

aka

# KDE Application Version, managed by release script
set (KDE_APPLICATIONS_VERSION_MAJOR "15")
set (KDE_APPLICATIONS_VERSION_MINOR "04")
set (KDE_APPLICATIONS_VERSION_MICRO "0")
set (KDE_APPLICATIONS_VERSION "${KDE_APPLICATIONS_VERSION_MAJOR}.${KDE_APPLICATIONS_VERSION_MINOR}.${KDE_APPLICATIONS_VERSION_MICRO}")

That script will patch this to the given version.

Like

./update_applications_version.pl CMakeLists.txt 15 04 3

or update an error if it didn't match all parts (with the template boilerplate code).

Greetings
Christoph

----- Ursprüngliche Mail -----
> El Dimarts, 23 de juny de 2015, a les 09:30:10, Christoph Cullmann va
> escriure:
> > > El Dimarts, 9 de juny de 2015, a les 07:52:49, Christoph Cullmann va
> > > 
> > > escriure:
> > > > Hi,
> > > > 
> > > > dear release team, would it make sense to have some script updated
> > > > KDE Application Release Version in CMake to auto-version the bundled
> > > > applications (if wanted by the application maintainer)?
> > > 
> > > How would you do that? Scripts doing magic are nice, but can you describe
> > > how the magic would work?
> > 
> > I would do the same like for frameworks.
> > 
> > All projects that are included in kde applications x.xx would have a CMake
> > variable like the frameworks
> > 
> > set(KF5_VERSION "5.12.0") # handled by release scripts
> > 
> > but (KDE Applications or whatever):
> > 
> > set(KA5_VERSION "15.04") # handled by release scripts
> > 
> > and after each release that gets auto-incremented to the next one.
> > 
> > Applications that want to use that, then can just define their own version
> > based on this var. Applications that don't want to use that, don't need to
> > do anything.
> 
> This looks doable, i think it makes sense to have three different variables
> major, minor, patch, so you can decide which ones to use.
> 
> Would you volunteer to work on such a script?
> 
> Cheers,
>   Albert
> 
> > 
> > Greetings
> > Christoph
> 
> 

-- 
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH      Email: cullmann at AbsInt.com
Science Park 1                         Tel:   +49-681-38360-22
66123 Saarbrücken                      Fax:   +49-681-38360-20
GERMANY                                WWW:   http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234


More information about the release-team mailing list