Summary: | [patch] bsd.port.mk: support systems that have been built WITHOUT_INFO=yes (no makeinfo & install-info) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | John E. Hein <jhein> | ||||||||||
Component: | Ports Framework | Assignee: | Port Management Team <portmgr> | ||||||||||
Status: | Closed FIXED | ||||||||||||
Severity: | Affects Only Me | CC: | bapt, ports | ||||||||||
Priority: | Normal | ||||||||||||
Version: | Latest | ||||||||||||
Hardware: | Any | ||||||||||||
OS: | Any | ||||||||||||
Attachments: |
|
Description
John E. Hein
2008-12-18 19:10:03 UTC
Responsible Changed From-To: freebsd-ports-bugs->portmgr Over to maintainer(s). The previous patch for bsd.ports.mk had some stray debug in it. That has been removed in a respin of the patch attached here... Are the ls + cat operations still required? Also, can a more experienced porter please look at this and provide some critiques? Thanks! -Garrett Garrett Cooper wrote at 19:53 -0800 on Dec 19, 2008: > Are the ls + cat operations still required? If you mean the stray debug I inadvertently had in the first patch, then no. Look at the later patch in the PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=129741 > Also, can a more experienced porter please look at this and provide > some critiques? Thanks for taking a look. bsd.port.mk has been updated a bit since I submitted this PR. The old patch still applies, but here's a refreshed one. Nothing changed in the patch except some line numbers. Fresh patch sitting in my ~ on freefall... -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Russians in the rear view mirror ... are closer than they appear. Getting back to this bug because I hit the same issue today with a new system, is it possible to do a simpler diff like the following? This patch wouldn't guard against users shooting themselves in the foot, but for folks who have actually configured a system appropriately so infopages aren't installed. I'm not changing the pkg-plist reference to INSTALL_INFO because it may taint the system if one's cross-compiling. This patch shouldn't be committed because a lot of ports need to be fixed with upstream patches (don't have knobs for --with-infopages, and conditional variables aren't being set in configure.{ac,in} for INSTALL_INFO, MAKEINFO, etc -- devel/libtool22 is a prime example). To be consistent with autoconf INSTALL_INFO and MAKEINFO are being spelled the way that they are. Thanks! -Garrett Infrastructure PR. this is still needed, I to think having a USES=info might be a good idea Imho the best approach here is to make the ports depend on print/texinfo if base was built WITHOUT_INFO A commit references this bug: Author: bapt Date: Sun Jun 15 21:38:30 UTC 2014 New revision: 357930 URL: http://svnweb.freebsd.org/changeset/ports/357930 Log: Make ports providing info files depending on print/textinfo if base has been built WITHOUT_INFO PR: 129741 Changes: head/Mk/bsd.port.mk |