- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.
While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.
Also, replace some EXTRACT_SUFX occurences with USES=tar:*.
Checked by: make fetch-urlall-list
With hat: portmgr
Sponsored by: Absolight
The ports infrastructure may insert additional content into the
BUILD_DEPENDS variable which is not supposed to be a run depend.
Approved by: portmgr (bapt)
system are tracked. Without this "fix", /usr/bin/sftp is not recongnized
to negate the build dependency of openssh-portable. [1]
- Bump PORTREVISION.
Discussed with: bdrewery [1]
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
-Update to May 26, 2011 snapshot:
Add support for OpenSSH's sftp-server umask option.
Remove inline references to satisify certain compilers
Remove the now unnecessary sftp-logging compatibility mode.
When getopt_long is not available, like on AIX, use bundled NetBSD
getopt_long.
Update the SECURITY document to include a reference to /etc/popt and \
~/.popt as they relate to rsync.
Fix for rsync-3.0 which now uses a short -e option, with an optional
argument as a server side option indicating protocol compatibility.
Fix scponly crash on Solaris
Fix detection and inclusion of getopt on certain platforms
Document risks associated with popt reading /etc/popt and ~/.popt
Document getopt requirement (when certain configure options are enabled)
- cleanup redundant BUILD_DEPENDS+= [1]
PR: ports/157804
Submitted by: Rob Farmer <rfarmer _at_ predatorlabs.net> (maintainer), ohauer [1]
Approved by: maintainer
-Drop long comment describing knobs - it just duplicates OPTIONS
-For SCPONLY_DEFAULT_CHDIR, print a note about setting it. I'm not sure if post-patch is the best place for this, though?
-Drop dead site and just use Sourceforge
-Use the PORTDOCS variable
-Install some useful docs and drop useless one (TODO)
-Drop pre-everything message about defaults changing; that was 5 years ago
-LOCALBASE vs. PREFIX correction
-Add post-install messages to the plist so package users see them too
PR: ports/153115
Submitted by: Rob Farmer <rfarmer@predatorlabs.net> (maintainer)
Rsync 3 needs the "-e" option, which is blocked without this patch by scponly
Patch pulled from upstream CVS, which states a full release will come soon:
http://lists.ccs.neu.edu/pipermail/scponly/2010-November/002170.html
Reported by: Frank Bartels <knarf _at_ knarf.de>
PR: 152869
Submitted by: Rob Farmer <rfarmer _at_ predatorlabs.net> (maintainer)
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
I'm finding that recently-created scponlyc chroots do not
provide a sufficient environment for /usr/libexec/sftp-server
to run. The sftp client symptom is just:
$ sftp user@www
Connecting to www...
Password:
Connection closed
$
The cause appears to be that recent versions of
/usr/libexec/sftp-server will complain about of lack of
access to /dev/null and exit, resulting in the closed
connection witnessed by the remote client.
The solution appears to be to create a devfs in the scponlyc
chroot.
To automatically create at boot time a devfs in the home
directory of each user of scponlyc, I have chosen to put a
script in /usr/local/etc/rc.d.
PR: ports/108009
Submitted by: Jim Long <list@museum.rain.com>
Approved by: maintainer timeout
From: Hideyuki KURASHINA <rushani@FreeBSD.org>
I've confirmed the rsync compatibility in scponly 4.4 is broken.
Unfortunately, at this moment I don't have enough time to
test the patch you showed us...
PR: ports/96295
Submitted by: UEDA Hiroyuki <ueda@drweb.jp>
o fixes that hopefully improve the optarg compilation situation
o UNISON $HOME environment fix
o fixes to setup_chroot.sh.in
PR: ports/92587
Submitted by: rushani (maintainer)
Update to 4.3. Highlights in this release,
- Compatibility of WinSCP in SCP mode improved.
- The scponlyc (chroot'ed version of scponly) works again.
PR: ports/91039
Submitted by: Hideyuki KURASHINA <rushani@FreeBSD.org>
1. Fix WinSCP compativility in SCP mode. PORTREVISION bumped.
2. Add sourceforge mirrors to ${MASTER_SITES}.
3. From scponly 4.2, scp & WinSCP compatibilities are not enabled
by default. Notice this at pre-everything target as well as
UPDATING.
PR: ports/90983
Submitted by: Hideyuki KURASHINA <rushani@FreeBSD.org>
depends a location of run-time link-editor. Since FreeBSD has
dynamic root capability from __FreeBSD_version == 501105, we
should add new location to unbreak the script.
PR: 59511
Submintted by: MAINTAINER
