developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
* Platform fixes for Tru64, Borland, Irix, HP-UX, AIX, UnixWare7
and Reliant UNIX
* Support for Intel C++
* Initial support for Qt/Embedded on FreeBSD
* more undocumented stuff
from pkg/DESCR:
tmake is an easy-to-use tool from Trolltech to create and maintain
makefiles for software projects. It can be a painful task to manage
makefiles manually, especially if you develop for more than one platform
or use more than one compiler. tmake automates and streamlines this
process and lets you spend your valuable time on writing code, not
makefiles.
Our main motivation for developing tmake was that we spent far too much
time maintaining makefiles for Qt,
our cross-platform GUI toolkit. Qt supports around 15 flavors of Unix,
Microsoft Windows, and around 15 different C++ compilers. We looked at
GNU autoconf, but it was Unix-specific and not flexible enough in our
opinion. Our makefile system also had to deal with Qt meta object compiler
(moc) issues. The moc program extracts meta information from C++ files and
generates a C++ file with data tables etc. It takes extra work to add
makefile rules for the moc and wanted to automate this task.
