Bug 25828 - The devel/autoconf port won't install install-sh
Summary: The devel/autoconf port won't install install-sh
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-15 13:50 UTC by Yar Tikhiy
Modified: 2001-12-24 14:36 UTC (History)
1 user (show)

See Also:


Attachments
file.diff (585 bytes, patch)
2001-03-15 13:50 UTC, Yar Tikhiy
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yar Tikhiy 2001-03-15 13:50:00 UTC
	It became a good tradition to include the install-sh script
	that came with autoconf in projects' source trees, so
	configure could use it as a last resort for the AC_PROG_INSTALL
	test.  However, install-sh is not installed by default as
	a part of autoconf.  Therefore, it would be convenient to
	add a couple lines to the port so the script gets installed
	and developers can copy in into their projects.

How-To-Repeat: 
	# find install-sh
Comment 1 Yar Tikhiy 2001-03-15 14:59:54 UTC
Oops, brain fart occured :-) Of course the "how to repeat" section should
read:
#  locate install-sh

Additionally, I've just found out that supplying install-sh is not a mere
tradition,
but a strict requirement of AC_PROG_INSTALL. Anyway, that makes my bug
report even more urgent :-)

-Yar
Comment 2 Mario Sergio Fujikawa Ferreira freebsd_committer freebsd_triage 2001-03-23 17:16:17 UTC
Responsible Changed
From-To: freebsd-ports->torstenb

He is the maintainer.
Comment 3 dwcjr freebsd_committer freebsd_triage 2001-08-31 05:21:02 UTC
Responsible Changed
From-To: torstenb->portmgr

Over to a more active maintainer who has vested interest in autoconf due to its importance in ports
Comment 4 Will Andrews freebsd_committer freebsd_triage 2001-12-23 11:06:11 UTC
State Changed
From-To: open->feedback

Hi, and sorry for the lack of response to this PR. 
I've just upgraded autoconf to 2.52 and would like to know if this is still 
a requirement of autoconf; if not, should I apply a similar patch to 
ports/devel/autoconf213?
Comment 5 Yar Tikhiy freebsd_committer freebsd_triage 2001-12-24 13:25:25 UTC
On Sun, Dec 23, 2001 at 03:07:00AM -0800, will@FreeBSD.org wrote:
> 
> I've just upgraded autoconf to 2.52 and would like to know if this is still
> a requirement of autoconf; if not, should I apply a similar patch to
> ports/devel/autoconf213?

As I can see, install-sh still should be placed into program's
sources if the program is to be configured with `configure'.
So I think install-sh should be provided by both ports.
It will be an absolutely harmless and safe change.

Please take a note that install-sh isn't required by autoconf itself.
However, a developer needs a copy of the script handy when starting
a new project utilizing autoconf because `configure' will look for it
in the project's source tree.

-- 
Yar
Comment 6 Will Andrews freebsd_committer freebsd_triage 2001-12-24 14:35:40 UTC
State Changed
From-To: feedback->closed

Fixed in the old autoconf 2.13 and new 2.52 as well.  Thank you and sorry 
for the tardiness in response.