Navigation:
Browse pkgsrc
(this page) 2012-09-14 04:48:32 by John Nemeth | Files touched by this commit (6) |  |
Log message: Remove this as the last remaining corresponding version of Asterisk has been removed. This is included in all existing packages and is expected to be included in any new packages. |
| 2010-09-22 04:25:13 by John Nemeth | Files touched by this commit (1) |
Log message: add a conflict with asterisk >= 1.6.2 as that will include the extra sounds |
| 2010-04-10 10:36:43 by Stephen Borrill | Files touched by this commit (2) |
Log message: Fix installation in non-DESTDIR case (hi joerg!) |
| 2010-03-17 16:16:55 by Joerg Sonnenberger | Files touched by this commit (2) |
Log message: Fix installation. |
2010-03-08 01:24:43 by John Nemeth | Files touched by this commit (1) |  |
Log message: - take over maintainship as I handle most Asterisk stuff - mark as destdir ready XXX The Makefile has a comment saying that "this program" is licensed under GPL. There is a README file saying that the sounds are licensed under a BSD licence. Need to check for updates and/or contact upstream for clarification and a proper licence file. XXX The PLIST needs some serious TLC. |
| 2009-06-14 20:31:59 by Joerg Sonnenberger | Files touched by this commit (6) |
Log message: Convert @exec/@unexec to @pkgdir or drop it. |
| 2009-06-14 19:38:43 by Joerg Sonnenberger | Files touched by this commit (44) |
Log message: Remove @dirrm entries from PLISTs |
| 2009-05-21 01:43:00 by Zafer Aydogan | Files touched by this commit (1) | |
Log message: update master site and homepage. |
| 2007-11-12 00:43:47 by Thomas Klausner | Files touched by this commit (1) |
Log message: Remove ftp1.digium.com from MASTER_SITES, does not resolve. |
| 2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257) |
Log message: 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. |
New packages: