This package include a C library and some sample programs that demonstrate
the library's power.
It is a cryptographic library: you can crypt any type of data. Key length
is unlimited. You can generate password, manage users, hide text in file,
etc.
ATTENTION!!! IN SOME COUNTRIES THIS SOFTWARE MAY BE ILLEGAL, SO DON'T USE
IT IF YOU ARE NOT ALLOWED.
WWW: http://www.encryptsolutions.com/
===> The following configuration options are available for bugs-4.1.1_3:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove expired ports:
2021-04-01 ftp/wzdftpd: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 astro/roadmap: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/cosmo: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/bomberinstinct: Unmaintained and dead upstream, does not build
with -fno-common (llvm 11)
2021-04-01 games/drm: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/bygfoot: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 games/cre: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 irc/hybserv: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 irc/xaric: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 mail/elmo: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 misc/cave: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 security/bugs: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 security/dmitry: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
(Only the first 15 lines of the commit message are shown above )
Extend expiration of ports broken with -fno-common
Extend the expiration of unmaintained leaf ports that are broken with
-fno-common and previously had a short expiration date. The new date is set
to 2021-04-01, meaning the ports will be in the 2021Q2 branch, giving people
until 2021-06-30 (10 months from now) to fix issues.
Improve the wording of the deprecation message, mentioning both llvm 11 and
-fno-common.
Bump portrevision to force reinstall. This way the warning message about
deprecation will be displayed to users installing or reinstalling the
software.
MFH: 2020Q3 (maybe)
Remove compatibility code for FreeBSD < 11.2 from all ports.
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
Fix file modes after extracting.
Some port's archives contains files modes that are a bit too restrictive
for some usage. For example:
BUILD_DEPENDS= ${NONEXISTENT}:foo/bar:configure
When building as a regular user, dependencies are installed/built as
root, so if the archive contains files that have a mode of, say, 600,
they will not be readable by the port requesting the dependency.
This will also fix broken distribution files where directories don't
have the executable bit on.
OSVERSION 1100077 is after base r283997:
Change directory permissions in pre-order.
In this order, it won't try to recurse into a directory for which it
doesn't have permission, before changing that permission.
This follows an existing behavior in other BSDs, linux, OS X.
PR: 213574
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
- Fix parallel builds: call make(1) correctly, register dependencies
- Drop LICENSE_FILE for a standard license (GPLv2)
- Respect CC and CFLAGS without patching of makefile (use MAKE_ARGS)
- Convert NOPORTDOCS -> PORT_OPTIONS:MDOCS, add OPTIONS_DEFINE
- Move "make test" under the wing of our standard regression-test target
- Generally cleanup Makefile and port description while I am here
For ports maintained by ports@FreeBSD.org, remove names and/or
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
