kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/misc/getopt/Makefile

25 lines
620 B
Makefile
Raw Normal View History

Fixed PKGMANDIR.
2006-10-21 13:11:34 +02:00
# $NetBSD: Makefile,v 1.7 2006/10/21 11:11:34 rillig Exp $
Initial import of getopt, a getopt(1) replacement supporting long options. Getopt(1) is a program to help shell scripts parse command-line parameters. It is for example included in the util-linux distribution (versions up to 2.7.1) for Linux. But, there were some problems with that getopt(1) implementation, as listed in the 'BUGS' section of its man-page: * Whatever getopt(3) has. * Arguments containing white space or imbedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. * The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of getopt; this again is hard to fix. * The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Additionally, the example in the manual-page does not run correctly (at least not with any bash shell I have tried). This implementation of getopt(1) solves some of these problems, while still staying (for all practical purposes) completely compatible with other getopt(1) implementations. It has replaced the old util-linux version, but it should be useful for other Unixes too.
2004-12-26 16:55:39 +01:00
#
DISTNAME= getopt-1.1.3
Recursive revision bump / recommended bump for gettext ABI change.
2006-02-06 00:08:03 +01:00
PKGREVISION= 1
Initial import of getopt, a getopt(1) replacement supporting long options. Getopt(1) is a program to help shell scripts parse command-line parameters. It is for example included in the util-linux distribution (versions up to 2.7.1) for Linux. But, there were some problems with that getopt(1) implementation, as listed in the 'BUGS' section of its man-page: * Whatever getopt(3) has. * Arguments containing white space or imbedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. * The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of getopt; this again is hard to fix. * The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Additionally, the example in the manual-page does not run correctly (at least not with any bash shell I have tried). This implementation of getopt(1) solves some of these problems, while still staying (for all practical purposes) completely compatible with other getopt(1) implementations. It has replaced the old util-linux version, but it should be useful for other Unixes too.
2004-12-26 16:55:39 +01:00
CATEGORIES= misc
MASTER_SITES= http://www.frodol.dds.nl/
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Initial import of getopt, a getopt(1) replacement supporting long options. Getopt(1) is a program to help shell scripts parse command-line parameters. It is for example included in the util-linux distribution (versions up to 2.7.1) for Linux. But, there were some problems with that getopt(1) implementation, as listed in the 'BUGS' section of its man-page: * Whatever getopt(3) has. * Arguments containing white space or imbedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. * The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of getopt; this again is hard to fix. * The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Additionally, the example in the manual-page does not run correctly (at least not with any bash shell I have tried). This implementation of getopt(1) solves some of these problems, while still staying (for all practical purposes) completely compatible with other getopt(1) implementations. It has replaced the old util-linux version, but it should be useful for other Unixes too.
2004-12-26 16:55:39 +01:00
HOMEPAGE= http://www.frodol.dds.nl/
COMMENT= Program to help shell scripts parse command-line parameters
Enable pkgviews installation.
2004-12-26 20:16:37 +01:00
PKG_INSTALLATION_TYPES= overwrite pkgviews
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions: USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-22 22:07:36 +02:00
USE_TOOLS+= gmake
Initial import of getopt, a getopt(1) replacement supporting long options. Getopt(1) is a program to help shell scripts parse command-line parameters. It is for example included in the util-linux distribution (versions up to 2.7.1) for Linux. But, there were some problems with that getopt(1) implementation, as listed in the 'BUGS' section of its man-page: * Whatever getopt(3) has. * Arguments containing white space or imbedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. * The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of getopt; this again is hard to fix. * The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Additionally, the example in the manual-page does not run correctly (at least not with any bash shell I have tried). This implementation of getopt(1) solves some of these problems, while still staying (for all practical purposes) completely compatible with other getopt(1) implementations. It has replaced the old util-linux version, but it should be useful for other Unixes too.
2004-12-26 16:55:39 +01:00
Fixed PKGMANDIR.
2006-10-21 13:11:34 +02:00
INSTALLATION_DIRS= bin ${PKGMANDIR}/man1
Enable pkgviews installation.
2004-12-26 20:16:37 +01:00
Initial import of getopt, a getopt(1) replacement supporting long options. Getopt(1) is a program to help shell scripts parse command-line parameters. It is for example included in the util-linux distribution (versions up to 2.7.1) for Linux. But, there were some problems with that getopt(1) implementation, as listed in the 'BUGS' section of its man-page: * Whatever getopt(3) has. * Arguments containing white space or imbedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. * The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of getopt; this again is hard to fix. * The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Additionally, the example in the manual-page does not run correctly (at least not with any bash shell I have tried). This implementation of getopt(1) solves some of these problems, while still staying (for all practical purposes) completely compatible with other getopt(1) implementations. It has replaced the old util-linux version, but it should be useful for other Unixes too.
2004-12-26 16:55:39 +01:00
do-install:
${INSTALL_PROGRAM} ${WRKSRC}/getopt ${PREFIX}/bin
Fixed PKGMANDIR.
2006-10-21 13:11:34 +02:00
${INSTALL_MAN} ${WRKSRC}/getopt.1 ${PREFIX}/${PKGMANDIR}/man1
Initial import of getopt, a getopt(1) replacement supporting long options. Getopt(1) is a program to help shell scripts parse command-line parameters. It is for example included in the util-linux distribution (versions up to 2.7.1) for Linux. But, there were some problems with that getopt(1) implementation, as listed in the 'BUGS' section of its man-page: * Whatever getopt(3) has. * Arguments containing white space or imbedded shell metacharacters generally will not survive intact; this looks easy to fix but isn't. * The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of getopt; this again is hard to fix. * The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell version to another. Additionally, the example in the manual-page does not run correctly (at least not with any bash shell I have tried). This implementation of getopt(1) solves some of these problems, while still staying (for all practical purposes) completely compatible with other getopt(1) implementations. It has replaced the old util-linux version, but it should be useful for other Unixes too.
2004-12-26 16:55:39 +01:00
.include "../../devel/gettext-lib/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink