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

50 lines
1.3 KiB
Makefile
Raw Normal View History

Revbump packages with a runtime Python dep but no version prefix. For the Python 3.8 default switch.
2020-12-04 21:44:57 +01:00
# $NetBSD: Makefile,v 1.27 2020/12/04 20:45:31 nia Exp $
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
#
DISTNAME= routeplanner_0.11
PKGNAME= routeplanner-cli-0.11
Revbump packages with a runtime Python dep but no version prefix. For the Python 3.8 default switch.
2020-12-04 21:44:57 +01:00
PKGREVISION= 6
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
CATEGORIES= misc
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=routeplanner/}
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
*: Convert broken sourceforge HOMEPAGEs back to http
2020-03-20 12:57:53 +01:00
HOMEPAGE= http://routeplanner.sourceforge.net/
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
COMMENT= Highway trip planner written in Python
Move WRKSRC definition away from the first paragraph in a Makefile.
2004-01-20 13:18:15 +01:00
WRKSRC= ${WRKDIR}/routeplanner-0.11
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
NO_BUILD= yes
Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by making PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable that specifies all of the tools we need to build/run the package.
2005-07-15 20:27:48 +02:00
USE_TOOLS+= gzip
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
No need to have two variables for the same logic. Replace PYTHON_PATCH_SCRIPTS with REPLACE_PYTHON.
2014-01-25 11:45:15 +01:00
REPLACE_PYTHON= rpcli
misc: align variable assignments pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-11-03 18:04:19 +01:00
RPLIBDIR= ${PREFIX}/lib/routeplanner
RPPY= rpcli.py rpcountry.py rpdbase.py rpunits.py rpcity.py rproute.py
RPDB= Basic-USA.rpl3 NorthAmerica.rpl3
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
RP_LIBDIR_SED= "s|/usr/share/routeplanner|${RPLIBDIR}|g"
Create directories before installing files into them.
2005-06-17 05:50:19 +02:00
INSTALLATION_DIRS= bin
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
post-patch:
for i in rpcli rpcli.py;do \
${MV} ${WRKSRC}/$$i ${WRKSRC}/$$i.tmp && \
${SED} ${RP_LIBDIR_SED} <${WRKSRC}/$$i.tmp >${WRKSRC}/$$i; \
done
do-install:
Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target.
2008-03-04 20:21:10 +01:00
${INSTALL_SCRIPT} ${WRKSRC}/rpcli ${DESTDIR}${PREFIX}/bin
${INSTALL_DATA_DIR} ${DESTDIR}${RPLIBDIR}
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
for i in ${RPPY}; do \
Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target.
2008-03-04 20:21:10 +01:00
${INSTALL_DATA} ${WRKSRC}/$$i ${DESTDIR}${RPLIBDIR}; \
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
done
for i in ${RPDB}; do \
Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target.
2008-03-04 20:21:10 +01:00
${GZIP_CMD} -c ${WRKSRC}/$$i >${DESTDIR}${RPLIBDIR}/$$i.gz; \
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
done
# optional speedup
misc: align variable assignments pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-11-03 18:04:19 +01:00
#PYTHON_VERSIONS_INCOMPATIBLE= 36 # py-kjbuckets
Convert to bl3.
2004-04-26 02:12:41 +02:00
#.include "../../devel/py-kjbuckets/buildlink3.mk"
#.include "../../devel/py-pqueue/buildlink3.mk"
import routeplanner-cli-0.11, a routeplanner written in Python (you'll probably not use it to plan the next trip, but it is still a good example for graph manipulation in Python)
2003-07-28 16:57:00 +02:00
.include "../../lang/python/application.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink