pkgsrc/inputmethod/skkserv, branch pkgsrc-2004Q2 [no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2004Q2 2004-04-27T20:51:10Z Installation of the RCD_SCRIPTS rc.d script is done automatic 2004-04-27T20:51:10Z reed reed@pkgsrc.org 2004-04-27T20:51:10Z urn:sha1:06e49aba4fe18f57de9dc3b2d192af2b4fbd4af0 here. So don't install it twice. (Anyways, ${PREFIX}/etc/rc.d is not the correct location; the RCD_SCRIPTS uses ${RCD_SCRIPTS_EXAMPLEDIR}.) mk/bsd.pkg.install.mk now automatically registers 2004-04-23T22:07:52Z reed reed@pkgsrc.org 2004-04-23T22:07:52Z urn:sha1:9c790735dbc3013a298acc48a2ea5bff9a0901cf the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too. Convert to bl3. 2004-04-18T23:58:29Z wiz wiz@pkgsrc.org 2004-04-18T23:58:29Z urn:sha1:5362fbfdddf356e3a7a82daf88a4743e28a2cf44 Move WRKSRC definition away from the first paragraph in a Makefile. 2004-01-20T12:18:15Z agc agc@pkgsrc.org 2004-01-20T12:18:15Z urn:sha1:3ad1bdbf063a03bdcca7087d41be98b07ad933af Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL if 2003-08-30T22:51:11Z jlam jlam@pkgsrc.org 2003-08-30T22:51:11Z urn:sha1:b2677a2cb0d685822071dbac41558e75e1bc7c6a USE_PKGINSTALL is "YES". bsd.pkg.install.mk will no longer automatically pick up a INSTALL/DEINSTALL script in the package directory and assume that you want it for the corresponding *_EXTRA_TMPL variable. Prepare for pkgviews by making sure that passing VIEW-INSTALL or 2003-08-30T20:22:49Z jlam jlam@pkgsrc.org 2003-08-30T20:22:49Z urn:sha1:2920a32c71bae3a6a02b2c5c0576d9a60b9a0594 VIEW-DEINSTALL to the INSTALL/DEINSTALL scripts don't cause errors. Convert to bsd.pkg.install.mk to handle the rc.d script. MESSAGE is removed 2003-07-29T22:08:28Z jmmv jmmv@pkgsrc.org 2003-07-29T22:08:28Z urn:sha1:7d7d16056f0d43a72b08513950f364faf95d4672 as the default install template provides the right standard information (or can be extended in a common way if needed ;). Bump PKGREVISION to 2. s/netbsd.org/NetBSD.org/ 2003-07-17T21:41:05Z grant grant@pkgsrc.org 2003-07-17T21:41:05Z urn:sha1:0155927c43fe3bf836adedcc6d232abb594c8eb7 Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02T01:15:31Z jschauma jschauma@pkgsrc.org 2003-06-02T01:15:31Z urn:sha1:e366d0c694f76afeff8379f738912bfa77414859 Should anybody feel like they could be the maintainer for any of thewe packages, please adjust. Complete standardization of messages according to latest pkglint. 2002-09-24T12:29:55Z wiz wiz@pkgsrc.org 2002-09-24T12:29:55Z urn:sha1:e8817c9088e66725a7ace239801ff1f75b6fc0e1