Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
|
|
|
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
|
|
|
|
- Bl3ify.
Tcl/Tk distfiles are not needed any more. Installed header files are
used instead.
- Enable pkgviews installation.
Bump PKGREVISION due to PLIST changes.
|
|
with 8.4 will be updated to depend on x11/tk after Tk update.
|
|
be updated to depend on lang/tcl after Tcl/Tk update.
|
|
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
|
|
|
|
|
|
Tcl and Tk
|
|
references of the pkglint package.
_PKGSRCDIR is an internal definition in bsd.pkg.mk, and a few packages
which would like to refer to other packages in the build tree. It should
not be set by users, but neither should it stop a user from building a
package if it is defined, so make it obvious that this is the case.
|
|
|
|
before!)
|
|
out the problem.
|
|
Similar to what Nick Hudson did for tcl-tclX.
|
|
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
<mark@MCS.VUW.AC.NZ> in PR pkg/12060. Some minor adjustments by me.
[incr Tcl] provides the extra language support needed to build large Tcl/Tk
applications. It introduces the notion of objects, which act as building
blocks for an application. Each object is a bag of data with a set of
procedures or "methods" that are used to manipulate it. Objects are organized
into "classes" with identical characteristics, and classes can inherit
functionality from one another. This object-oriented paradigm adds another
level of organization on top of the basic variable/procedure elements, and
the resulting code is easier to understand and maintain.
|