Next | Query returned 27 messages, browsing 21 to 30 | previous

History of commit frequency

CVS Commit History:


   2005-12-29 07:22:26 by Johnny C. Lam | Files touched by this commit (597)
Log message:
Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
   2005-12-05 21:51:20 by Roland Illig | Files touched by this commit (1432)
Log message:
Fixed pkglint warnings. The warnings are mostly quoting issues, for
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in

    http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
   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-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.
   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-12-01 10:53:04 by Thomas Klausner | Files touched by this commit (13)
Log message:
"the the" -> "the"
   2004-10-11 18:51:54 by David Brownlee | Files touched by this commit (9) | Imported package
Log message:
Importwhoson-2.03
Whoson ("WHO iS ONline") is a proposed Internet protocol that allows
Internet server programs know if a particular (dynamically allocated)
IP address is currently allocated to a known (trusted) user and,
optionally, the identity of the said user.

The protocol could be used by an SMTP Message Transfer System in
conjunction with anti-spam-relaying filters to implement a scheme
similar to the one described here to allow roaming customers use
their "home" SMTP server to submit email while connected from a
"foreign" network.


Next | Query returned 27 messages, browsing 21 to 30 | previous