Something in the dependency chain for dnsip6 rebuilds when conf-home
is updated. By creating it before the build and then moving it over
later the timestamp is before all the built binaries. Since we
purposely remove all installer-related files, only those will be
rebuilt.
Reported by: brd
unexpectedly getting readline from ports if it's already installed.
- Add patch to work with newer libreadline
- Provide an option to use libedit from ports, avoiding the libedit in base.
- Note 1: The patch to work with newer libreadline is only applied in the
libreadline case since it actually breaks building with libedit.
- Note 2: libreadline is not BSD licensed and while libedit would be
preferable, it seems to have issues with UTF8 still, see ruby bug 9204. Once
that's resolved, we can make libedit the default.
PR: ports/187928 [1] (based on)
PR: ports/188077 [2] (based on)
Submitted by: Shin-ya Murakami <murashin@gfd-dennou.org> [1]
Submitted by: Christoph Moench-Tegeder <cmt@burggraben.net> [2]
Obtained from: http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/ext/readline/readline.c?r1=43458&r2=45225 (ruby upstream)
MFH: 2014Q2
This port was using an unecessary roll-your-own extraction to control
where it was extracted. Just let the standard mechanisms extract the
second tarball and move in the post-extract target.
Also:
* minor alignment
* pet portlint
* reset maintainer (MIA for 16 months)
ChangeLog:
* R:
i) Tuned Newton iteration algorithms in ngreg and ngreg.proj.
ii) Bug fixes in routines involving univariate minimization via
nlm0.
iii) Minor changes in makedata.x's.
Despite all 6 distribution files being zip archives, the extraction target
is using a tar-specific set of arguments. USES=zip cannot be used (native
or infozip) so explicitly require ${TAR} for future-proofing reasons.
Approved by: Infrastructure blanket
dfVFS, or Digital Forensics Virtual File System, provides read-only access to
file-system objects from various storage media types and file formats. The goal
of dfVFS is to provide a generic interface for accessing file-system objects,
for which it uses several back-ends that provide the actual implementation of
the various storage media types, volume systems and file systems.
WWW: https://code.google.com/p/dfvfs/