===> The following configuration options are available for husky-fidoconf-1.9.20201211_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Fix WWW in parent/child ports
Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
a) just using the pkg-descr from the parents
b) or had their own separate pkg-descr with custom WWW
Use WWW?= in parents when the child's WWW is different.
Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.
Approved by: portmgr (implicit)
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 )
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
Rework husky ports to use a more conventional MASTER/SLAVE port pattern.
- Remove Makefile.local as it is intended to be a user file that should
not be committed. Its documentation is poor (r12873) but users are
relying on it.
- Remove CONFLICTS as for every port it just conflicted with itself.
With hat: portmgr
news/husky-(fidoconf|htick|hpt) : builds INFO pages everywhere again
Jan Beich fixed the info pages (thanks Jan!) so this enables their
building for htick and fidoconf of FreeBSD 11 and DragonFly. While here,
commit USES+=makeinfo to -hpt that went uncommitted accidently yesterday.
news/husky-fidoconf: Test feature rather than OPSYS/OSVERSION
Testing for OPSYS/OSVERSION requires <pre> and <post> inclusions and
isn't necessary. All we need is the same logic that USES=makeinfo uses.
This simplifies previous commit.
news/husky(-fidoconf): Unbreak F11 and DragonFly (old texi files)
The reason all husky ports were bumped is because the -devel package
suffix was not removed as intended. It's been removed now so all husky
packages have different names.
The fidoconf package uses texi files to build an info page and an html
page. It appears there is no man page equivalent. I couldn't find a
patch to fix the old-format texi files that the latest texinfo programs
can read, so I blocked them from building on FreeBSD 11 and DragonFly
where the port was broken.
While here, I removed %%PORTDOCS%% from man pages. There were installed
unconditionally (as they should be), so setting DOCS option to off would
have broken the port as well. Also use the INFO definition as it should
be rather than hardcoding the pkg-plist.
The maintainer will be notified so he can prepare a patch for texi or
update the port.
Approved by: blanket (unbreaks F11)
Remove '-devel' prefix from husky* ports
Today the older unstaged husky-* ports were removed as the first part
of a transition move the development versions into their place. This
commit completes the relocation of husky-*-devel ports.
news/husky*: Remove Husky ports to pave way for next version
In a two-step process, the Husky ports that are due to be removed
on September 1 are being removed now. The next step will be to rename
the husky-*-devel ports to plain husky-*
Approved by: former maintainer (fjoe@)