Mailinglist Archive: opensuse-kde (249 mails)

< Previous Next >
Re: [opensuse-kde] KDE_VERSION_STRING in kdelibs4, is the release number *really* needed?
  • From: Andreas Jaeger <aj@xxxxxxxxxx>
  • Date: Mon, 19 Apr 2010 09:58:12 +0200
  • Message-id: <201004190958.13639.aj@xxxxxxxxxx>
On Saturday 17 April 2010 11:47:29 Cristian Morales Vega wrote:
The kdelibs4 spec file in KDE:KDE4:Factory:Desktop has:

#
# define KDE version exactly
#
sed -ri "s,#cmakedefine KDE_VERSION_STRING
\"@KDE_VERSION_STRING@\",#cmakedefine KDE_VERSION_STRING
\"@KDE_VERSION_STRING@ \\\\\"release $(echo %release | cut -d.
-f-1)\\\\\"\"," kdecore/util/kdeversion.h.cmake

So every time kdelibs4 is rebuilt:
- Even if it has no changes (but the KDE_VERSION_STRING in the header)
the package is published for users to download
- So every package that depends on kdelibs4 is rebuilt
- Most of these packages get a modification because of the
KDE_VERSION_STRING in the header (every app with an "About box") and
so are also published for users to download

We could save build power and bandwidth without the RPM release number
in KDE_VERSION_STRING. So, why it is there? I don't see what we gain
having "the KDE version defined exactly".

I agree, let's remove the change... Any volunteers?

Andreas
--
Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
< Previous Next >