QCAD has been largely rewritten since the previous version
(QCAD 2) was updated in pkgsrc, meaning that the changes are
vast. From the authors website:
QCAD 3 comes with a new and improved CAD engine which improves
performance (spatial index) and allows for advanced property
editing and future extensions (dynamic properties). The other
major addition is a powerful and complete ECMAScript interface.
New interactive tools can be developed with a few lines of
ECMAScript but even entire new applications can be developed
using QCAD technology. QCAD 3 is also the first QCAD version
that fully supports the DWG format as well as various different
versions of the DXF format.
The complete ChangeLog is at http://www.qcad.org/en/changelog
Problems found with existing distfile for eagle:
distfiles/eagle-lin32-7.4.0.run
No changes made to eagle/distinfo file.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
patches to add it). Drop pax from the default USE_TOOLS list.
Make bsdtar the default for those places that wanted gtar to extract
long links etc, as bsdtar can be built of the tree.
1.5.4 release was something of a toy, QCad was thoroughly reworked for 2.0
and could now be called usable for many practical purposes.
Versions 2.0.4.0 (initially) to 2.0.5.0 have been usable in wip for a bit
more than a year, and so seem ready to import.
"Yes, that should be fine. Please watch the bulk builds for it and
try to fix any problems that might appear." -wiz@
Updates to pkglint now produce some new suggestions, which I will make and
commit after confirming they don't break anything; at least this version I
already know to build successfully for me.
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.
without affecting packages that are currently using it.
Packages which previously didn't set BUILDLINK_DEPMETHOD to neither "full" nor
"build" now set it to "full", but should be checked whether they really need it
(comment added). Packages which previously set it to "build" now don't set it
anymore.
Ok by jlam, wiz.
