(which is not) throughout the ports Makefiles.
* Replace find|xargs with find -exec {} +
* Replace -exec {} \; with -exec {} + if applicable.
* Use the -delete operator to remove files and empty directories.
* Combine and tweak some find(1) invocations while here.
ok kn@ rsadowski@ espie@
an "infrastructure" port, won't have library conflict problems, and as
Ingo says, 'Groff does not really use C++, it is merely "C with classes"'
and this is not expected to change.
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
in ASCII output finally got committed upstream. Use it in OpenBSD
right away, such that related work on mandoc can proceed.
Maybe we can even improve libm documentation before release.
to just "OpenBSD": that's the obvious thing to do, no idea why i
didn't do it long ago. So far, man(7) had no default at all, and
the "OpenBSD ports" used by mdoc(7) no longer makes sense because
only about 25 ports use groff nowadays, and none of those use mdoc(7).
This change is also simplifies groff-mandoc comparisons.
stage are marked as .PHONY, or make(1) might consider some of them
up to date, skipping the fake install for them and causing later
packaging to fail.
Also regenerate the patch with make update-patches.
No package change (as far as it built at all), no bump.
Issue observed by Jerome Ibanes <jibanes at gmail dot com> on sparc64.
OK sthen@
* we no longer change the rendering of the bullet character
* avoid groff warning "unbalanced .el request" when running with -mdoc -ww
* improve rendering of large braces in UTF-8 output (accepted upstream)
* bump REVISION
ok sthen@ naddy@
For those cases where the build succeeded, no bump needed because
the package doesn't change; for those cases where parallel builds
failed, no bump needed either. Committing quickly to fix the build.
ok sthen@
new features:
* glilypond(1) - new preprocessor for music typesetting
* gperl(1) - new preprocessor for embedding Perl code in roff documents
* gpinyin(1) - new preprocessor to pretty-print Pinyin syllables
* groff_mom(7) now has full eqn(7), pic(7), and tbl(7) support
* mdoc(7) now supports the %C macro (already available in mandoc)
* various bugfixes
* many of our patches have been integrated upstream
* changing the bullet is no longer needed, mandoc can now handle it
ok sthen@ naddy@
1) For man(7), initialize internal numerical registers correctly
such that a stray .RE without a preceding .RS doesn't set the left
margin to column 0. Reported by bentley@ on discuss at mdocml.
Patch technically approved by Werner Lemberg (upstream).
The only reason it isn't committed upstream yet is that FSF
pesters me to sign a Copyright Assignment contract under
Massachusetts legislature, talking about Warranties and whatnot,
which i resist.
2) Restore correct syntax to the .ie cascade governing section titles
that i broke, trying to be too clever. Problem reported by
David Levine via pascal@ after the nmh(1) folks added an OpenBSD
machine to their buildbot cluster.
ok pascal@
committed upstream. It already works in mandoc(1), and it is used in
some OpenBSD base system manuals, and using it is generally encouraged,
so having it in our groff port as well really makes sense.
ok bentley@ on August 1, 2013 (and i forgot to commit after unlock, sorry)
when a man(7) input file contains two consecutive .TP lines.
This bugfix improves the formatting of unzip(1), for example.
While here, recognize 5.4 as an OpenBSD version in mdoc(7) files.
ok sthen@ dcoppa@ espie@
* New features: gropdf(1), pdfmom(1)
* Lots of our patches were accepted upstream, lots of upstream bug fixes.
Tested by landry@ and pascal@, ok landry@ and sthen@.
do not print "OpenBSD 5.0" but "OpenBSD ports".
While here, remove some noise from the groff build log.
Bump the groff package.
Technically, this changes the contents of all packages that USE_GROFF,
but please refrain from bumping the world: Having "OpenBSD 5.0" in
the footers of some ports manual until they are updated the next time,
or until the next libc bump if they aren't, is not a real problem.
string "OpenBSD ports" suggested and patch ok'ed by sthen@
Build fonts before using them; fixes parallel builds as tested by naddy@.
In case we ever support PDF, don't break parallel builds; ok pascal@.
These are all purely build system fixes; no package change, no bump.
* Unbreak groff manuals by using tbl(1); reported by pascal@.
* Deal with our Mdocdate cvs keyword; as designed by jmc@ in 2007.
* Use troffrc for OpenBSD config changes; suggested by Werner Lemberg.
* Unbreak the hdtbl examples; from upstream.
* Volume names in man(7) page headers; suggested by Yuri Pankov.
* Update various string tables; coordinated with upstream.
* Add a README explaining local changes; using feedback from pascal@.
* Better description and bump.
ok pascal@, and tested in an i386 bulk build by naddy@, thanks!
because mandoc(1) doesn't like them, with the exception
of groff_mdoc(7), which is derived from the traditional
mdoc.samples(7) and which is just fine with mandoc(1).
Problem reported and fix tested by <Pascal dot Stumpf at cubes dot de>.
naddy@ and deraadt@ agree with the general direction
Solar Designer did an audit of temp file handling in groff-1.20.
He found and fixed *lots* of ugliness, but most does not look
exploitable and some was already improved in groff-1.21.
This is my own fix for the only one that, with a huge amount of extra
paranoia, might be worth patching. To mount an exploit, the attacker
would need to trick root into setting an unusable TMPDIR (or similar)
variable in the environment such that mktemp -d fails, then convince
root to run pdfroff (*you* don't run that as root, do you?), then
handle a race condition to find the PID and predict the temp file
name to mount a symlink attack.
"I think we should still go for the fix" jasper@
Lots of new functionality, lots of bug fixes, and bringing in
significant maintenance efforts from upstream.
To name just one specific example, the number of arguments mdoc(7)
macros can take is no longer limited.
Two of the more tricky patches contributed by naddy@, thanks!
Tested in bulk builds by landry@.
Tested on sparc (GCC 2) by phessler@ and on alpha (GCC 3) by naddy@.
ok naddy@, landry@
Before using this to build ports, make sure you install
the src/usr.sbin/pkg_add/OpenBSD/PackingElement.pm patch
i'm going to commit right afterwards as well, or you will end up
with ports manuals containing ANSI escape sequences.
