Re: kdelibs binNMU on s390

[Sune Vuorela <nospam@vuorela.dk>]

On 2007-09-23, Sune Vuorela <nospam@vuorela.dk> wrote:
> My plan is to change uname -m usage to dpkg-architecture usage in this
> case and then ask for a binNMU on all archs where there is a small
> change that uname -m and dpkg-architecture -qDEB_BUILD_ARCH differs.
> And trying to add appropriate qt vs kdelibs versioned conflicts.
> (Feedback on this part, please)

This is actually quite much bigger than I expected. the uname -m is at
least encoded in any package matching kde-style* and used. it is also
encoded in some files in /usr/lib - at least in gwenview.
and in stuff shippnig files in /usr/lib/kde3/plugins/designer/ 

for the files in plugins/designer and the stuff in kde-style-*, it
doesn't work if the so-called buildkey string differs from the file and
to how qt was build now.

The "buildkey" string is encoded in qconfig.h:
$ grep -i QT_BUI /usr/include/qt3/qconfig.h
#define QT_BUILD_KEY "i686 Linux g++-4.* full-config"  where it is
generated by "uname -m" "uname -s" "compilerversion" "config options"

for example:
:/usr/lib/kde3/plugins/styles$ strings serenity.so | grep buildkey
buildkey=i686 Linux g++-4.* full-config


I don't completely know how to proceed here. (And is this the
appropriate place?)

/Sune