2005-05-02 22:34:09 by Jeremy C. Reed | Files touched by this commit (172) |
Log message:
RCD_SCRIPTS_EXAMPLEDIR is no longer customizable.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
|
2005-04-28 16:11:13 by Thomas Klausner | Files touched by this commit (2) |
Log message:
Add CONFLICTS with lsh (common man page).
|
2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539) |
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
|
2005-02-24 14:10:14 by Alistair G. Crooks | Files touched by this commit (192) |
Log message:
Add RMD160 digests.
|
2005-01-14 06:15:40 by Johnny C. Lam | Files touched by this commit (15) |
Log message:
Create a pam.buildlink3.mk file that is used by PAM-using packages.
It includes the correct buildlink3.mk file from either Linux-PAM
(security/PAM) or OpenPAM (security/openpam) and eventually will
support solaris-pam. pam.buildlink3.mk will:
* set PAMBASE to the base directory of the PAM files;
* set PAM_TYPE to the PAM implementation used.
There are two variables that can be used to tweak the selection of
the PAM implementation:
PAM_DEFAULT is a user-settable variable whose value is the default
PAM implementation to use.
PAM_ACCEPTED is a package-settable list of PAM implementations
that may be used by the package.
Modify most packages that include PAM/buildlink3.mk to include
pam.buildlink3.mk instead.
|
2004-12-28 03:47:52 by Jeremy C. Reed | Files touched by this commit (156) |
Log message:
The default location of the pkgsrc-installed rc.d scripts is now
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
|
2004-10-03 02:18:40 by Todd Vierling | Files touched by this commit (863) |
Log message:
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
2004-06-15 20:44:57 by Krister Walfridsson | Files touched by this commit (16) |
Log message:
Resurrect openssh+gssapi per request of jwise@.
|
2004-04-27 21:08:36 by Johnny C. Lam | Files touched by this commit (4) | |
Log message:
Don't support the updating the in-tree openssh via pkgsrc. pkgsrc really
has no business trying to update parts of the base system.
|
2004-04-24 00:08:00 by Jeremy C. Reed | Files touched by this commit (109) |
Log message:
mk/bsd.pkg.install.mk now automatically registers
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.
|