Changes:
* Make use of eina.
* Fix string in list and hash.
* Fix array in eet_data.
* Add crypto support to eet with OpenSSL.
* Add GNUtls support to eet.
* Make password callback work with GNUtls.
* Add a function to retrieve raw signature.
* Fix a corrupted pointer use in eet_cipher.c
* Add some missing __UNUSED__ flags.
* Fix problem reported by llvm
* Add sha1 retrieval for an Eet_File.
* Force fsync() after data is written to file, solve ext4 issues.
* Disable fsync. Edit the code if you need it.
* Make eet_data thread safe.
* Fix eet pkg-config dependencies.
* Fix double init of gcry.
* Release eet 1.2.0
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
Changes:
- Fixes to data codecs (data descriptors).
- Fixes for non-existing files opened READ/WRITE and other
miscellanouse bugs found.
- Speedups for decoding and lookups, make inline-image decode better
on some platforms and add signed-eet file support as well as opening
eet files from memory.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
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.
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.
