Re: [NEW] fonts/annapurna
George Rosamond writes: > George Rosamond: > > George Rosamond: > >> From the pkg/DESCR: > >> > >> Annapurna is a Unicode-based font family with support for the many > >> diverse languages that use the Devanagari script. The design is > >> intended to be highly readable, reasonably compact and visually > >> attractive to produce quality publications. These fonts are names > >> after the majestic Annapurna mountain range of Nepal. > >> > > > > Confused the DISTFILE suffix with the tarball. Reattached as .tgz > > Ping. > > New tarball with a small correction to pkg/DESCR. This one is also ok bentley@, with the correction that it also looks to be OFL instead of "OFL-like custom license".
Re: Should games/fifengine be marked as broken on sparc64?
Kaashif Hymabaccus writes: > games/fifengine's Makefile has the line: > > > BROKEN-sparc64 =out of memory when compiling fifePYTHON_wrap.cxx > > Which was added in a commit with this message: > > > Don't try building fifengine on archs that will definitely run out > > of memory. > > I can build it on my sparc64 box with no issue if I remove the > BROKEN-*. I guess if it uses more than 4 GB of memory, 32 bit > architectures can't possibly build it, so it being BROKEN on i386 is > probably accurate. > > But there's nothing stopping someone with enough RAM from building > this on sparc64, so why is it marked as BROKEN? I believe you. But I mark such ports as broken when they consistently fail to build in bulks. Maybe the bulk builder could succeed it with a bit more memory, but as it is it currently wastes a lot of time on a system that already takes a long long time to build packages. http://build-failures.rhaalovely.net//sparc64/2017-11-12/games/fifengine.log http://build-failures.rhaalovely.net//sparc64/2017-11-22/games/fifengine.log http://build-failures.rhaalovely.net//sparc64/2017-12-03/games/fifengine.log http://build-failures.rhaalovely.net//sparc64/2017-12-17/games/fifengine.log -- Anthony J. Bentley
Re: memcached: default to loopback
Hi,
On Mon, Feb 26, 2018 at 05:15:24PM +, Stuart Henderson wrote:
> memcached installations are currently being actively used as DoS amplifiers.
> Can we change the default to listen on loopback only?
I like it. If committed, it probably should also get a remark in
current.html.
Ciao,
Kili
> Index: Makefile
> ===
> RCS file: /cvs/ports/misc/memcached/Makefile,v
> retrieving revision 1.41
> diff -u -p -r1.41 Makefile
> --- Makefile 11 Jan 2018 19:27:04 - 1.41
> +++ Makefile 26 Feb 2018 17:14:47 -
> @@ -4,7 +4,7 @@ COMMENT= distributed memory object cachi
>
> DISTNAME=memcached-1.5.3
> CATEGORIES= misc
> -REVISION=0
> +REVISION=1
>
> HOMEPAGE=https://www.memcached.org/
>
> Index: pkg/README
> ===
> RCS file: /cvs/ports/misc/memcached/pkg/README,v
> retrieving revision 1.2
> diff -u -p -r1.2 README
> --- pkg/README17 Jul 2017 08:35:08 - 1.2
> +++ pkg/README26 Feb 2018 17:14:47 -
> @@ -4,13 +4,20 @@ $OpenBSD: README,v 1.2 2017/07/17 08:35:
> | Running ${FULLPKGNAME} on OpenBSD
> +---
>
> -Memcached relies on SASL as authentication mechanisms, if you could not
> -use it, it should be firewalled accordingly. You may wish
> -to add a rule such as the following to /etc/pf.conf:
> +From the upstream documentation, "Memcached does not spend much, if any,
> +effort in ensuring its defensibility from random internet connections.
> +So you must not expose memcached directly to the internet, or otherwise
> +any untrusted users. Using SASL authentication here helps, but should
> +not be totally trusted."
>
> - block on $ext_if proto tcp to ($ext_if) port 11211
> +The default setting in this package is now to listen on localhost only.
> +
> +To change to listening on all IP addresses (upstream's default), assuming
> +you have already firewalled appropriately:
> +
> +# rcctl set memcached flags '-u _memcached'
>
> An alternative is to listen on a unix socket in /var/run/memcached/sock,
> granting write permissions to users in group _memcached.
>
> -#rcctl set memcached flags '-u _memcached -s /var/run/memcached/sock -a 0660'
> +# rcctl set memcached flags '-u _memcached -s /var/run/memcached/sock -a
> 0660'
> Index: pkg/memcached.rc
> ===
> RCS file: /cvs/ports/misc/memcached/pkg/memcached.rc,v
> retrieving revision 1.4
> diff -u -p -r1.4 memcached.rc
> --- pkg/memcached.rc 11 Jan 2018 19:27:04 - 1.4
> +++ pkg/memcached.rc 26 Feb 2018 17:14:47 -
> @@ -3,7 +3,7 @@
> # $OpenBSD: memcached.rc,v 1.4 2018/01/11 19:27:04 rpe Exp $
>
> daemon="${TRUEPREFIX}/bin/memcached -d"
> -daemon_flags="-u _memcached"
> +daemon_flags="-u _memcached -l 127.0.0.1"
>
> . /etc/rc.d/rc.subr
>
memcached: default to loopback
memcached installations are currently being actively used as DoS amplifiers.
Can we change the default to listen on loopback only?
Index: Makefile
===
RCS file: /cvs/ports/misc/memcached/Makefile,v
retrieving revision 1.41
diff -u -p -r1.41 Makefile
--- Makefile11 Jan 2018 19:27:04 - 1.41
+++ Makefile26 Feb 2018 17:14:47 -
@@ -4,7 +4,7 @@ COMMENT=distributed memory object cachi
DISTNAME= memcached-1.5.3
CATEGORIES=misc
-REVISION= 0
+REVISION= 1
HOMEPAGE= https://www.memcached.org/
Index: pkg/README
===
RCS file: /cvs/ports/misc/memcached/pkg/README,v
retrieving revision 1.2
diff -u -p -r1.2 README
--- pkg/README 17 Jul 2017 08:35:08 - 1.2
+++ pkg/README 26 Feb 2018 17:14:47 -
@@ -4,13 +4,20 @@ $OpenBSD: README,v 1.2 2017/07/17 08:35:
| Running ${FULLPKGNAME} on OpenBSD
+---
-Memcached relies on SASL as authentication mechanisms, if you could not
-use it, it should be firewalled accordingly. You may wish
-to add a rule such as the following to /etc/pf.conf:
+From the upstream documentation, "Memcached does not spend much, if any,
+effort in ensuring its defensibility from random internet connections.
+So you must not expose memcached directly to the internet, or otherwise
+any untrusted users. Using SASL authentication here helps, but should
+not be totally trusted."
- block on $ext_if proto tcp to ($ext_if) port 11211
+The default setting in this package is now to listen on localhost only.
+
+To change to listening on all IP addresses (upstream's default), assuming
+you have already firewalled appropriately:
+
+# rcctl set memcached flags '-u _memcached'
An alternative is to listen on a unix socket in /var/run/memcached/sock,
granting write permissions to users in group _memcached.
-#rcctl set memcached flags '-u _memcached -s /var/run/memcached/sock -a 0660'
+# rcctl set memcached flags '-u _memcached -s /var/run/memcached/sock -a 0660'
Index: pkg/memcached.rc
===
RCS file: /cvs/ports/misc/memcached/pkg/memcached.rc,v
retrieving revision 1.4
diff -u -p -r1.4 memcached.rc
--- pkg/memcached.rc11 Jan 2018 19:27:04 - 1.4
+++ pkg/memcached.rc26 Feb 2018 17:14:47 -
@@ -3,7 +3,7 @@
# $OpenBSD: memcached.rc,v 1.4 2018/01/11 19:27:04 rpe Exp $
daemon="${TRUEPREFIX}/bin/memcached -d"
-daemon_flags="-u _memcached"
+daemon_flags="-u _memcached -l 127.0.0.1"
. /etc/rc.d/rc.subr
Should games/fifengine be marked as broken on sparc64?
games/fifengine's Makefile has the line: > BROKEN-sparc64 =out of memory when compiling fifePYTHON_wrap.cxx Which was added in a commit with this message: > Don't try building fifengine on archs that will definitely run out > of memory. I can build it on my sparc64 box with no issue if I remove the BROKEN-*. I guess if it uses more than 4 GB of memory, 32 bit architectures can't possibly build it, so it being BROKEN on i386 is probably accurate. But there's nothing stopping someone with enough RAM from building this on sparc64, so why is it marked as BROKEN? -- Kaashif Hymabaccus GPG: 3E810B04
Re: [NEW] fonts/scheherazade
Anthony J. Bentley: > On Mon, Feb 19, 2018 at 9:21 AM, George Rosamond > wrote: >> George Rosamond: >>> from pkg/DESCR: >>> >>> Scheherazade is a TrueType extended Unicode Arabic font. >>> >>> Scheherazade supports most of the Unicode 8.0 Arabic character >>> repertoire (excluding the Arabic Presentation Forms blocks, which >>> are not recommended for normal use). >>> >>> Font smarts are implemented using OpenType and Graphite technologies. >>> A number of glyph variations are accessible through font features >>> available via both OpenType and Graphite technologies. > > The license marker says "OFL-like custom license", but it appears to > be straight OFL 1.1. > > Other than that it looks fine to me. ok, anyone? > New tarball attached, Anthony. Thanks. g scheherazade-2.100.tgz Description: Binary data
[UPDATE] sysutils/sleuthkit
Hi, this is the diff to update sleuthkit to latest release. Ok? Cheers, Remi. Index: Makefile === RCS file: /cvs/ports/sysutils/sleuthkit/Makefile,v retrieving revision 1.22 diff -u -p -u -p -r1.22 Makefile --- Makefile 31 Oct 2017 21:38:28 - 1.22 +++ Makefile 26 Feb 2018 14:00:58 - @@ -2,7 +2,7 @@ COMMENT= forensic toolkit based on TCT -DISTNAME= sleuthkit-4.5.0 +DISTNAME= sleuthkit-4.6.0 CATEGORIES= sysutils security SHARED_LIBS += tsk 1.0 # 17.0 Index: distinfo === RCS file: /cvs/ports/sysutils/sleuthkit/distinfo,v retrieving revision 1.12 diff -u -p -u -p -r1.12 distinfo --- distinfo 31 Oct 2017 21:38:28 - 1.12 +++ distinfo 26 Feb 2018 14:00:58 - @@ -1,2 +1,2 @@ -SHA256 (sleuthkit-4.5.0.tar.gz) = 906xbnF1mAVqVmSuhC2KzSdqz8NA6Ou9h9CUgWfniaw= -SIZE (sleuthkit-4.5.0.tar.gz) = 8611141 +SHA256 (sleuthkit-4.6.0.tar.gz) = 9SoIqw3geBgsDy0Z0+GzQUJKngwWM6YcO4kvs4+ay5c= +SIZE (sleuthkit-4.6.0.tar.gz) = 8634432
[UPDATE] sysutils/py-tsk
Hi,
this is the diff to update py-tsk to latest release.
Ok?
Cheers,
Remi.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/py-tsk/Makefile,v
retrieving revision 1.5
diff -u -p -u -p -r1.5 Makefile
--- Makefile 9 Nov 2017 20:42:46 - 1.5
+++ Makefile 26 Feb 2018 10:03:01 -
@@ -2,7 +2,7 @@
COMMENT = Python bindings for The Sleuth Kit (libtsk)
-MODPY_EGG_VERSION = 20171108
+MODPY_EGG_VERSION = 20180225
DISTNAME = pytsk3-${MODPY_EGG_VERSION}
PKGNAME = py-tsk-${MODPY_EGG_VERSION}
@@ -30,7 +30,7 @@ pre-configure:
LIB_DEPENDS = sysutils/sleuthkit \
devel/libtalloc
-TEST_DEPENDS = sysutils/py-tsk=${MODPY_EGG_VERSION}
+TEST_DEPENDS = sysutils/py-tsk${MODPY_FLAVOR}=${MODPY_EGG_VERSION}
# it needs test_data/* in the Github repository
do-test:
Index: distinfo
===
RCS file: /cvs/ports/sysutils/py-tsk/distinfo,v
retrieving revision 1.5
diff -u -p -u -p -r1.5 distinfo
--- distinfo 9 Nov 2017 20:42:46 - 1.5
+++ distinfo 26 Feb 2018 10:03:01 -
@@ -1,2 +1,2 @@
-SHA256 (pytsk3-20171108.tar.gz) = CqTF6yZ3oh+goruGv89JJ1JvImuZ4EXS204wEZ6AaWo=
-SIZE (pytsk3-20171108.tar.gz) = 2953931
+SHA256 (pytsk3-20180225.tar.gz) = 2Bjk5yL06r+aCbip+AzhD6tmNBXcDoZ4c7ux+MBg7Pc=
+SIZE (pytsk3-20180225.tar.gz) = 3149373
Re: Sourceforge changes causing problems. Where the wild Tcl extensions are.
On Mon, Feb 26, 2018 at 12:31:05PM +0100, Marc Espie wrote: > On Sat, Feb 24, 2018 at 02:32:27PM +0200, Svyatoslav Mishyn wrote: > > Hi, > > > > (Sat, 24 Feb 10:10) Stuart Henderson: > > > On 2018/02/24 00:05, Stuart Cassoff wrote: > > > > Chiselapp is Fossil. > > > > I'm just starting to look into this and so far I can get what seems to > > > > be a tarball from this very pretty url: > > > > > > > > https://chiselapp.com/user/schelte/repository/dbus/tarball/dbus-92d71c1d63.tar.gz?uuid=92d71c1d639645ab73811e7edfd946d3e449ad695510ff6abfc1c9bff9a372c3 > > > > > > > > These two extensions are now on Chiselapp and I know there will be > > > > others. > > > > (most?) Tcler's prefer Chiselapp over GitHub. > > > > Maybe there's a way to fit this nicely into the ports system, like is > > > > currently done with GitHub? > > > > > > It works ok without the uuid parameter, I would try > > > > > > MASTER_SITES= > > > https://chiselapp.com/user/schelte/repository/dbus/tarball/ > > > DISTNAME= dbus-92d71c1d63 > > > > if without uuid, then default will be "trunk" branch. > > see: https://chiselapp.com/user/schelte/repository/dbus/help?cmd=/tarball > > > > So, in that case DISTNAME should be "dbus-trunk". > > I fail to see how being required to specify a full uid in non ambiguous > cases is a win... > > Maybe talk to the people a chiselapp ? there's a reason most modern version > systems allow shortened uuid... > chiselapp is based on fossil repository (same as devel/fossil in port tree). the /tarball URL manual page is at http://fossil-scm.org/index.html/help?cmd=/tarball "r=" (or "uuid=" which is kept for backwards compatibility) is mandatory for querying a specific version (if omit, the default value is "trunk"). It could be a full uid *or* a shorten one. The name (passed as "name=" query parameter or directly in the URL) is whatever you want (no need to include the revision in the name). The following are the same (modulo the filename, which is present in the tarball, resulting different checksum): - https://chiselapp.com/user/schelte/repository/dbus/tarball/dbus-92d71c1d63.tar.gz?uuid=92d71c1d639645ab73811e7edfd946d3e449ad695510ff6abfc1c9bff9a372c3 - https://chiselapp.com/user/schelte/repository/dbus/tarball/dbus.tar.gz?uuid=92d71c1d639645ab73811e7edfd946d3e449ad695510ff6abfc1c9bff9a372c3 - https://chiselapp.com/user/schelte/repository/dbus/tarball/dbus.tar.gz?uuid=92d71c1d63 - https://chiselapp.com/user/schelte/repository/dbus/tarball/dbus.tar.gz?r=92d71c1d63 Thanks. -- Sebastien Marie
[UPDATE] sysutils/libsmraw
Hi,
this is the diff to update libsmraw to latest release.
Ok?
Cheers,
Remi.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/libsmraw/Makefile,v
retrieving revision 1.4
diff -u -p -u -p -r1.4 Makefile
--- Makefile 30 Nov 2017 14:27:23 - 1.4
+++ Makefile 26 Feb 2018 09:58:25 -
@@ -2,10 +2,9 @@
COMMENT = library and tools to access the (split) RAW image format
-VERSION = 20170803
+VERSION = 20180123
DISTNAME = libsmraw-alpha-${VERSION}
PKGNAME = ${DISTNAME:S/-alpha//}
-REVISION = 0
SHARED_LIBS += smraw 0.1 # 1.0
Index: distinfo
===
RCS file: /cvs/ports/sysutils/libsmraw/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 3 Nov 2017 13:44:32 - 1.2
+++ distinfo 26 Feb 2018 09:58:25 -
@@ -1,2 +1,2 @@
-SHA256 (libsmraw-alpha-20170803.tar.gz) = LFB7n9ZiLLrYtl7z6HldUcKTl5dXNUp0fHaUJpRTwKo=
-SIZE (libsmraw-alpha-20170803.tar.gz) = 1549204
+SHA256 (libsmraw-alpha-20180123.tar.gz) = ZqMCfzshjfHJ4XLFSUkrJOYN4bNQwHhcq/M8Jw5nQZw=
+SIZE (libsmraw-alpha-20180123.tar.gz) = 1558801
[UPDATE] sysutils/libsmdev
Hi,
this is the diff to update libsmdev to latest release.
Ok?
Cheers,
Remi.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/libsmdev/Makefile,v
retrieving revision 1.3
diff -u -p -u -p -r1.3 Makefile
--- Makefile 21 Nov 2017 00:13:03 - 1.3
+++ Makefile 26 Feb 2018 09:51:23 -
@@ -2,10 +2,9 @@
COMMENT = library to access to storage media devices
-VERSION = 20170225
+VERSION = 20171112
DISTNAME = libsmdev-alpha-${VERSION}
PKGNAME = ${DISTNAME:S/-alpha//}
-REVISION = 0
SHARED_LIBS += smdev 0.0 # 1.0
Index: distinfo
===
RCS file: /cvs/ports/sysutils/libsmdev/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 8 Apr 2017 04:26:26 - 1.2
+++ distinfo 26 Feb 2018 09:51:23 -
@@ -1,2 +1,2 @@
-SHA256 (libsmdev-alpha-20170225.tar.gz) = ql0crDwjtGrcnGnovMmzeCz79ssMKrf70sWjmymfzAQ=
-SIZE (libsmdev-alpha-20170225.tar.gz) = 1185544
+SHA256 (libsmdev-alpha-20171112.tar.gz) = vAZZ06P8Qxk2FGkOAn4dWdzu5Fqu1J8DG17K7j+MUlw=
+SIZE (libsmdev-alpha-20171112.tar.gz) = 1187736
[UPDATE] sysutils/libfvde
Hi,
this is the diff to update libfvde to latest release.
Ok?
Cheers,
Remi.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/libfvde/Makefile,v
retrieving revision 1.4
diff -u -p -u -p -r1.4 Makefile
--- Makefile 17 Feb 2018 19:45:37 - 1.4
+++ Makefile 26 Feb 2018 10:07:11 -
@@ -2,10 +2,9 @@
COMMENT = library and tools to access FileVault Drive Encryption
-VERSION = 20170930
+VERSION = 20180108
DISTNAME = libfvde-experimental-${VERSION}
PKGNAME = ${DISTNAME:S/-experimental//}
-REVISION = 0
SHARED_LIBS += fvde 0.1 # 1.0
Index: distinfo
===
RCS file: /cvs/ports/sysutils/libfvde/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 2 Nov 2017 17:38:19 - 1.2
+++ distinfo 26 Feb 2018 10:07:11 -
@@ -1,2 +1,2 @@
-SHA256 (libfvde-experimental-20170930.tar.gz) = Bph/0zh1MdPnflInnEBjUw36L6V0/+VsoZp+B0cCqRM=
-SIZE (libfvde-experimental-20170930.tar.gz) = 1678823
+SHA256 (libfvde-experimental-20180108.tar.gz) = sdPyUFlACAASLDPOCgX0cvG6Ezm17FAghqS4fzccXMI=
+SIZE (libfvde-experimental-20180108.tar.gz) = 1685341
[UPDATE] security/libewf
Hi,
this is the diff to update libewf to latest release.
Ok?
Cheers,
Remi.
Index: Makefile
===
RCS file: /cvs/ports/security/libewf/Makefile,v
retrieving revision 1.7
diff -u -p -u -p -r1.7 Makefile
--- Makefile 26 Nov 2017 19:51:30 - 1.7
+++ Makefile 26 Feb 2018 09:55:24 -
@@ -2,10 +2,9 @@
COMMENT = access the Expert Witness Compression Format
-VERSION = 20170703
+VERSION = 20171104
DISTNAME = libewf-experimental-${VERSION}
PKGNAME = libewf-${VERSION}
-REVISION = 0
SHARED_LIBS += ewf 1.0 # 3.0
Index: distinfo
===
RCS file: /cvs/ports/security/libewf/distinfo,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 distinfo
--- distinfo 4 Nov 2017 10:49:22 - 1.2
+++ distinfo 26 Feb 2018 09:55:24 -
@@ -1,2 +1,2 @@
-SHA256 (libewf-experimental-20170703.tar.gz) = hP4SOJq6z2PeotkhtjYiC7f9oyYtHEZ/bURaXjH1Ot4=
-SIZE (libewf-experimental-20170703.tar.gz) = 2230913
+SHA256 (libewf-experimental-20171104.tar.gz) = zzbTuvOpbb5Wb95Vrn15/C57mYgGqxPg9pkVeZ8Z4EA=
+SIZE (libewf-experimental-20171104.tar.gz) = 2243405
Re: Sourceforge changes causing problems. Where the wild Tcl extensions are.
On Sat, Feb 24, 2018 at 02:32:27PM +0200, Svyatoslav Mishyn wrote: > Hi, > > (Sat, 24 Feb 10:10) Stuart Henderson: > > On 2018/02/24 00:05, Stuart Cassoff wrote: > > > Chiselapp is Fossil. > > > I'm just starting to look into this and so far I can get what seems to be > > > a tarball from this very pretty url: > > > > > > https://chiselapp.com/user/schelte/repository/dbus/tarball/dbus-92d71c1d63.tar.gz?uuid=92d71c1d639645ab73811e7edfd946d3e449ad695510ff6abfc1c9bff9a372c3 > > > > > > These two extensions are now on Chiselapp and I know there will be others. > > > (most?) Tcler's prefer Chiselapp over GitHub. > > > Maybe there's a way to fit this nicely into the ports system, like is > > > currently done with GitHub? > > > > It works ok without the uuid parameter, I would try > > > > MASTER_SITES= > > https://chiselapp.com/user/schelte/repository/dbus/tarball/ > > DISTNAME= dbus-92d71c1d63 > > if without uuid, then default will be "trunk" branch. > see: https://chiselapp.com/user/schelte/repository/dbus/help?cmd=/tarball > > So, in that case DISTNAME should be "dbus-trunk". I fail to see how being required to specify a full uid in non ambiguous cases is a win... Maybe talk to the people a chiselapp ? there's a reason most modern version systems allow shortened uuid...
UPDATE: misc/cdrdaw
this updates cdrdao from 1.2.0 to 1.2.1. I had toc2cue creating empty files for
me,
which is apparently fixed in 1.2.1.
Otherwise not tested.
tests, comments, or even OK?
Sebastian
Index: Makefile
===
RCS file: /cvs/ports/misc/cdrdao/Makefile,v
retrieving revision 1.42
diff -u -r1.42 Makefile
--- Makefile26 Jul 2017 22:45:26 - 1.42
+++ Makefile26 Feb 2018 10:10:13 -
@@ -2,8 +2,7 @@
COMMENT= write audio/data CD-Rs in disk-at-once mode
-DISTNAME= cdrdao-1.2.0
-REVISION = 4
+DISTNAME= cdrdao-1.2.1
CATEGORIES=audio misc
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=cdrdao/}
Index: distinfo
===
RCS file: /cvs/ports/misc/cdrdao/distinfo,v
retrieving revision 1.6
diff -u -r1.6 distinfo
--- distinfo18 Jan 2015 03:14:30 - 1.6
+++ distinfo26 Feb 2018 10:10:13 -
@@ -1,2 +1,2 @@
-SHA256 (cdrdao-1.2.0.tar.gz) = yMMMPdtoKFjFZJUXs0aB2MyaxiXN6se+7GdxwL0FqSY=
-SIZE (cdrdao-1.2.0.tar.gz) = 2041966
+SHA256 (cdrdao-1.2.1.tar.gz) = dA3aTE6IdU1KWZfNUTC0Vp38sMkSO6asrtPCZqyZgWI=
+SIZE (cdrdao-1.2.1.tar.gz) = 1728003
Index: patches/patch-trackdb_CueParser_cc
===
RCS file: patches/patch-trackdb_CueParser_cc
diff -N patches/patch-trackdb_CueParser_cc
--- patches/patch-trackdb_CueParser_cc 21 May 2010 20:30:52 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,11 +0,0 @@
-$OpenBSD: patch-trackdb_CueParser_cc,v 1.1 2010/05/21 20:30:52 espie Exp $
trackdb/CueParser.cc.orig Fri May 21 22:28:20 2010
-+++ trackdb/CueParser.cc Fri May 21 22:28:25 2010
-@@ -23,6 +23,7 @@
-
- #include "Cue2Toc.h"
-
-+class Toc;
- extern Toc *parseToc(const char* tocBuffer, const char *filename);
-
- Toc *parseCue(FILE *fp, const char *filename)
Index: pkg/PFRAG.audio
===
RCS file: /cvs/ports/misc/cdrdao/pkg/PFRAG.audio,v
retrieving revision 1.1
diff -u -r1.1 PFRAG.audio
--- pkg/PFRAG.audio 4 Jun 2005 23:12:31 - 1.1
+++ pkg/PFRAG.audio 26 Feb 2018 10:10:13 -
@@ -1,2 +1,2 @@
@comment $OpenBSD: PFRAG.audio,v 1.1 2005/06/04 23:12:31 fgsch Exp $
-bin/toc2mp3
+@bin bin/toc2mp3
Re: NEW: devel/qp
On Wed, Feb 14, 2018 at 2:11 AM, Anthony J. Bentley wrote: > On Sat, Jan 27, 2018 at 8:12 PM, Anthony J. Bentley > wrote: >> On Fri, Jan 5, 2018 at 2:27 AM, Anthony J. Bentley >> wrote: >>> QP/C (Quantum Platform in C) is a lightweight, open source software >>> framework/RTOS for building reactive real-time embedded applications as >>> systems of cooperating, event-driven active objects (actors). The QP/C >>> framework is a member of a larger QP family consisting of QP/C, QP/C++, and >>> QP-nano frameworks, which are all strictly quality controlled, thoroughly >>> documented, and commercially licensable. >>> >>> >>> This port includes QP/C and QP/C++, but not QP-nano, as it doesn't >>> include a POSIX port like the others. >>> >>> I've seen this framework used in several embedded projects. If you >>> want to test it, there are some simple examples (which don't make >>> sense to install) under examples/posix that you can compile with >>> "gmake INCLUDES=-I/usr/local/include/qpc" (or qpcpp). >>> >>> ok? Still looking for oks for this port. See above for a simple way to test it. qp.tar.gz Description: GNU Zip compressed data
Re: [NEW] fonts/scheherazade
On Mon, Feb 19, 2018 at 9:21 AM, George Rosamond wrote: > George Rosamond: >> from pkg/DESCR: >> >> Scheherazade is a TrueType extended Unicode Arabic font. >> >> Scheherazade supports most of the Unicode 8.0 Arabic character >> repertoire (excluding the Arabic Presentation Forms blocks, which >> are not recommended for normal use). >> >> Font smarts are implemented using OpenType and Graphite technologies. >> A number of glyph variations are accessible through font features >> available via both OpenType and Graphite technologies. The license marker says "OFL-like custom license", but it appears to be straight OFL 1.1. Other than that it looks fine to me. ok, anyone?
