sansi was written to strip the ANSI control sequences in files, or
output, often, but not limited to those generated by compilers. I
found it difficult to visually grope/grep the output of script(1)
sessions. Especially with the advent of clang. While it's nice to
replay the script(1) sessions to view the highlighted messages.
It's near impossible to read it inline in your favorite pager, or
text editor;
Enter sansi.
*/*: Remove BROKEN in all ports that uses bsdforge.com for MASTER_SITES
Site is now back up
Reported by: Jamie Landeg-Jones <jamie@catflap.org>, Chris
<portmaster@bsdforge.com>
Approved by: portmgr (blanket)
*/*: Mark all ports that uses bsdforge.com in MASTER_SITES broken
The domain bsdforge.com has expired, mark all ports that only
uses bsdforge.com as broken (unfetchable). Additionally set ports that
uses bsdforge.com as primary site and have broken mirrors as broken
too as they're also unfetchable.
Approved by: portmgr (blanket)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
sansi was written to strip the ANSI control sequences in files, or
output, often, but not limited to those generated by compilers. I
found it difficult to visually grope/grep the output of script(1)
sessions. Especially with the advent of clang. While it's nice to
replay the script(1) sessions to view the highlighted messages.
It's near impossible to read it inline in your favorite pager, or
text editor;
Enter sansi.
WWW: http://BSDforge.com/projects/textproc/sansi/
PR: 195661
Submitted by: portmaster@bsdforge.com
