[Bug 234000] editors/nano: Remove groff dependency

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234000

            Bug ID: 234000
           Summary: editors/nano: Remove groff dependency
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: danilo at FreeBSD.org
          Reporter: daniel_eisele at gmx.de
             Flags: maintainer-feedback?(danilo at FreeBSD.org)
          Assignee: danilo at FreeBSD.org

Created attachment 200098
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200098&action=edit
Diff of editors/nano/Makefile

I just upgraded to 12.0 noticed that the nano port suddenly had about 80 new
dependencies. The reason for this is that the DOCS option depends on groff,
which was removed from the base system with 12.0 (base r319664), so now groff
and all its dependencies are installed when building nano.

The nano configure script checks for groff and, if it's available, uses it to
compile each of the 3 manpages (nano.1, rnano.1 and nanorc.5) into an HTML
page.
But all this isn't actually needed, as all of the HTML files are already
included in the original .tar.gz file, which means that they can just be
copied. This is probably the best and easiest solution.

Another solution would be to use mandoc instead of groff. mandoc can also
generate HTML, but the result is not exactly the same as with groff.

Also I think that the post-configure and post-build target can be removed, as
they only try to search and replace some text which doesn't exist anymore.

Diff is attached, it should work exactly the same whether groff is installed or
not, because the groff-generated files would just be overwritten with the
already included HTML files. (I didn't actually tested this, as I didn't want
to install groff)

Also other ports which depend on groff might have the same problem...

-- 
You are receiving this mail because:
You are the assignee for the bug.