Some developers may be doing their work using Qt Commercial. Adding support to Qt ebuild scripts to handle the downloading of the qt commercial packages in place of the qt-free packages is desired. A rough proposed patch to the existing qt ebuild will be attached for comment. Reproducible: Always Steps to Reproduce: 1. 2. 3. A Qt commercial install is almost exactly the same as a Qt free install. Major differences: 1) The gz/bz2 file is downloaded from a private ftp site, requiring a username/password 2) A valid Qt commercial license file must exist in the installer's home directory. I attempt to solve problem 1 by checking for the QT_COMMERCIAL environment variable before executing the ebuild. If it is set, then the ebuild attempts to download the commercial package instead of the free package. #2 *should* already be installed prior to running the ebuild. Hannes Mehnert said some problems may arise with the sandbox and checking of this license file (the license file check is done by Qt's configure script). Comments are welcome.
Created attachment 9824 [details, diff] add qt-commercial functionality to qt ebuild script This patch adds optional build support for qt-commercial via the environment variable QT_COMMERCIAL. A username/password combo will need to be stored in environment variables QT_COMMERCIAL_USER/QT_COMMERCIAL_PASS if the source package needs to be downloaded. The proper license file should already be downloaded and installed in ~/.qt-license package md5sums will also need to be added to the digest
Meh, about time for WONTFIX? :)
good for me.
