It is. Where is a good reference for seeing what names changed to what? I will need to manually update the links, etc.. that the TQt3 build script creates. But to what?

Here is what I have to update in my TQt3 package() function:

# install qmake install -D -m755 qmake/qmake ${pkgdir}${_prefix}/bin/qmake

# install doc pages which are missed by make install install -d -m755 "${pkgdir}${_prefix}/doc/" cp -r "${srcdir}/${pkgname#*-}/doc" "${pkgdir}${_prefix}/doc"

# install link the apps provided by qt3 so we don't collide with # qt4 and can run them. ln -sf "${_prefix}/bin/assistant" "${pkgdir}${_prefix}/bin/tqt3assistant" ln -sf "${_prefix}/bin/designer" "${pkgdir}${_prefix}/bin/tqt3designer" ln -sf "${_prefix}/bin/linguist" "${pkgdir}${_prefix}/bin/tqt3linguist" ln -sf "${_prefix}/bin/lrelease" "${pkgdir}${_prefix}/bin/tqt3lrelease" ln -sf "${_prefix}/bin/lupdate" "${pkgdir}${_prefix}/bin/tqt3lupdate" ln -sf "${_prefix}/bin/moc" "${pkgdir}${_prefix}/bin/tqt3moc" ln -sf "${_prefix}/bin/qmake" "${pkgdir}${_prefix}/bin/tqt3qmake" ln -sf "${_prefix}/bin/qtconfig" "${pkgdir}${_prefix}/bin/tqt3config"

# Build ld.so.conf file install -d -m755 "${pkgdir}/etc/ld.so.conf.d/" echo "${_prefix}/lib" >> "${pkgdir}/etc/ld.so.conf.d/${pkgname#*-}.conf"

# Build and install qt.profile install -d -m755 "${pkgdir}/etc/profile.d/" echo "export QTDIR=${_prefix}" > "${pkgdir}/etc/profile.d/${pkgname#*-}.sh" echo "export QT_XFT=true" >> "${pkgdir}/etc/profile.d/${pkgname#*-}.sh" echo "export PATH+=:${_prefix}/bin"

...

...

"${pkgdir}/etc/profile.d/${pkgname#*-}.sh"

echo "export PKG_CONFIG_PATH+=:${_prefix}/pkgconfig" >> "${pkgdir}/etc/profile.d/${pkgname#*-}.sh"

I was going to ask whether your build script explicitly copies those files to the package directory. The sym link crap seems to be an historic after-effect. All of the original Slackware build scripts for Qt3 did that too. I stopped installing TQt3 to an oddball location. I install TQt3 directly to /opt/trinity, which means the executable bin files all are installed to /opt/trinity/bin. No sym links required.

Here is a list of the bin files from the package I built last night:

Renamed:

opt/trinity/bin/tqmake opt/trinity/bin/tqmoc opt/trinity/bin/tquic opt/trinity/bin/tqdesigner opt/trinity/bin/tqassistant opt/trinity/bin/tqlinguist opt/trinity/bin/tqlrelease opt/trinity/bin/tqlupdate opt/trinity/bin/tqtconfig opt/trinity/bin/tqembed

Not renamed:

opt/trinity/bin/createcw opt/trinity/bin/qm2ts opt/trinity/bin/mergetr opt/trinity/bin/makeqpf opt/trinity/bin/msg2qm

Darrell

On 06/20/2012 08:34 PM, Timothy Pearson wrote:

I just added this comment to the bug report with the new names: http://bugs.pearsoncomputing.net/show_bug.cgi?id=843#c10

Bear in mind that Qt3 itself is unaffected, and as TQt3 is automatically generated from Qt3, Qt3 will continue to be maintained as it always has. Any pure Qt3 apps which don't build under TQt3 due to a lack of conversion can still be built/run with Qt3 as long as you don't mind forfeiting Qt4 or putting up with collisions between Qt3 and Qt4.

Tim

Thanks Tim,

I have always thought that preserving a pristine Qt3 and generating TQt3 was one of the wisest aspects of TDE design.