Something obviously changed within the framework, but I'm confused
how MASTER_SITES was never defined for bcc:
===> bcc-1995.03.12_1 depends on file: /usr/local/sbin/pkg - found
=> bcc.tar.gz doesn't seem to exist in /distfiles/.
===> /!\ Warning /!\
The :DEFAULT group used for bcc.tar.gz is missing
from MASTER_SITES. Check for typos, or errors.
=> Couldn't fetch it - please try to retrieve this
=> port manually into /distfiles/ and try again.
*** Error code 1
Strangely it's an Warning on FreeBSD 10.3 and an Error on DF. The
result is the same though: impossible to fetch.
PR: ports/136065 ports/127469
Submitted by: N.J. Mann <njm@njm.me.uk> and Aldis Berjoza <killasmurf86@gmail.com>
- Early identify port CONFLICTS
PR: 137855
Submitted by: Piotr Smyrak <smyru@heron.pl>
- Add --no-same-permissions to the EXTRACT_AFTER_ARGS command.
Tijl Coosemans has been reported an issue that when root is extracting from the
tarball, and the tarball contains world writable files
(sysutils/policykit as an example), there is a chance that the files
gets changed by malicious third parties right after the extraction,
which makes it possible to inject code into the package thus compromise
the system.
Submitted by: Tijl Coosemans <tijl@coosemans.org> Xin LI (delphij@)
- Fix some whitespaces
Tested with: exp-run
It is able to handle 16-bit code as well, and comes with an own
assembler and loader. (They are already known from Minix and Linux as
the `bin86' package.)
With a bit of `dd' magic, bcc can be used to compile messdos programs.
