Commit graph

9 commits

Author SHA1 Message Date
jlam
7820875fff Remove the abuse of buildlink that was pkg-config/buildlink3.mk. That
file's sole purpose was to provide a dependency on pkg-config and set
some environment variables.  Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.

For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
2005-08-10 20:56:10 +00:00
wiz
d774725534 Change path from devel/pkgconfig to devel/pkg-config.
No PKGREVISION bump since pkg-config is only a BUILD_DEPENDS.
2005-07-21 16:29:42 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
agc
4a3d2f7ce2 Add RMD160 digests. 2005-02-23 22:24:08 +00:00
tv
a08eeb5308 libtool/buildlink3.mk (now libltdl/buildlink3.mk) should only be used
if libltdl is needed; otherwise use USE_LIBTOOL.
2004-10-15 11:31:48 +00:00
minskim
737b87cc0f No need to include libtool/buildlink3.mk; defining USE_LIBTOOL is enough. 2004-10-13 09:23:08 +00:00
minskim
9566a67fd4 Override eet.pc. No PKGREVISION bump because this package was
imported a few minutes ago.
2004-10-13 09:21:36 +00:00
minskim
fe045558ae eet is not in pkgsrc-wip any more. 2004-10-13 09:03:35 +00:00
minskim
2cae23d96e Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me.
EET is a tiny library designed to write an arbitrary set of chunks of
data to a file and optionally compress each chunk (very much like a
zip file) and allow fast random-access reading of the file later on.
It does not do zip as a zip itself has more complexity than is needed,
and it was much simpler to implement this once here.

EET is extremely fast, small and simple.  EET files can be very small
and highly compressed, making them very optimal for just sending
across the Internet without having to archive, compress or decompress
and install them.  They allow for lightning-fast random-access reads
once created, making them perfect for storing data that is written
once (or rarely) and read many times, but the program does not want to
have to read it all in at once.

It also can encode and decode data structures in memory, as well as
image data for saving to EET files or sending across the network to
other machines, or just writing to arbitrary files on the system.  All
data is encoded in a platform independent way and can be written and
read by any architecture.
2004-10-13 08:57:55 +00:00