Age | Commit message (Collapse) | Author | Files | Lines |
|
don't have version information. Suggested by wiz@.
|
|
|
|
|
|
provided by Michal Pasternak via pkgsrc-wip
HTML documentation for Twisted Python; see py-twisted package for details.
|
|
provided by Michal Pasternak via pkgsrc-wip
Twisted is a framework, written in Python, for writing networked applications.
It includes implementations of a number of commonly used network services such
as a web server, an IRC chat server, a mail server, a relational database
interface and an object broker. Developers can build applications using all of
these services as well as custom services that they write themselves. Twisted
also includes a user authentication system that controls access to services
and provides services with user context information to implement their own
security models.
|
|
The tracker works under Python 2.2 and supports 3.3 clients properly.
The client is unchanged.
|
|
HTTP is only one view of the data moved around by Entropy).
|
|
|
|
to insert/retrieve content by the native FCP protocol rather than the
WWW proxy. From the DESCR:
=====
The most important tools for those who want to insert their own content as a
website into Freenet or Entropy, are the Freenet Tools (or similiar tools
from other authors :). For Freenet, there are some such programs linked from
their http://freenetproject.org) pages. Not many of them will work with
Entropy out-of-the-box, as they sometimes specialize on minor deviations in
the FCP interface. Specificially the newer tools, supporting the FEC FCP
v1.1 will fail with Entropy, as Entropy does not yet fully support the
changes to the Freenet Client Protocol. So I suggest you use ft for Entropy
for now, since I can help you there with problems or questions.
|
|
|
|
From the DESCR:
=====
ENTROPY is developed as a response to increasing censorship and surveillance
in the internet. The program connects your computer to a network of machines
which all run this software. The ENTROPY network is running parallel to the
WWW and also other internet services like FTP, email, ICQ. etc.
For the user the ENTROPY network looks like a collection of WWW pages. The
difference to the WWW however is that there are no accesses to central
servers. And this is why there is no site operator who could log who
downloaded what and when. Every computer taking part in the ENTROPY network
(every node) is at the same time server, router for other nodes, caching
proxy and client for the user: that is You.
|
|
|
|
pkgsrc since gkrellm1-snmp conversion to net-snmp.
|
|
|
|
|
|
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links)
use the new format correctly.
|
|
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example
buildlink[23].mk files in bsd.buildlink[23].mk.
|
|
|
|
|
|
PR pkg/24947; bump PKGREVISION.
|
|
Bump PACKAGEREVISION.
Noted by Michal Pasternak on tech-pkg.
|
|
|
|
Buildlink files: RECOMMENDED version changed to current version.
|
|
this. Fixes build on -current.
|
|
|
|
configure script was checking for YACC wrong (like .../bin/usr/pkg/bin/bison).
|
|
From PR pkg/23650 by Luc Beurton luc at black-kettle dot univ-ubs dot fr.
While here claim stewardship, use subst.mk framework, and fix a typo
in a patch file.
Bump PKGREVISION.
|
|
the curses.h -> ncurses.h symlink.
|
|
the ncurses.h -> curses.h link.
|
|
That should close PR 24818.
|
|
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
|
|
inclusion of python/application.mk to the end of Makefile's and fixing
paths to files. Bump PKGREVISION of this package to 1.
|
|
|
|
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that
we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
|
|
|
|
NSD 2.0.1 release notes:
BUG FIXES:
- Queries for QTYPE DS (DNSSEC) were not handled correctly in
certain cases.
- Partial support for unknown RRs. Known RR types with
unknown RR data format is not yet supported.
- Bug #75: Fixed bad error message when nsdc update is run for
the first time.
- Bug #78: Multiple zones, each with include directives, are
now compiled correctly.
|
|
Approved by agc.
|
|
testing for sys_nerr, so that this compiles on NetBSD. Add a patch
for the re-generated configure script. Fixes a problem noticed in
recent bulk builds.
|
|
|
|
in post-patch. Fixes a strange build error on sparc64.
|
|
This version fixes lots of bugs, adds more bandwidth savings, and
improves support for peers behind dynamic IPs.
|
|
|
|
for SunOS only. Okayed by maintainer, tron@.
(Also this checks for SunOS and /usr/include/netinet/ip6.h for IPv6
support, maybe the OPSYS check can be removed; but this is not
changed in this patch.)
|
|
The rc.d scripts are based on official NetBSD scripts.
This also adds:
CONFIGURE_ARGS+=--sysconfdir=${PKG_SYSCONFDIR}
This was discussed and okayed with maintainer, fredb, in February,
Currently, the ntpd.sh rc.d script has a note about the
ntpd_chrootdir is only for NetBSD at this time. (Because I haven't
tested under other operating systems.)
|
|
(Also should depend on gindent, but not fixed here.)
|
|
Oops, there's no nbcompat.h here. Put real #includes.
|
|
|
|
Temporary hack for Interix: for some reason, the detection of getpgrp()
having no arguments is failing there.
|
|
Add a utimes() stub for Interix.
(this change also needs to go in othersrc/usr.bin/tnftp)
|
|
bootstrap.
ok'd by lukem.
|