Re: Remove x11/mrxvt?
Frederic Cambus writes: > Hi ports@, > > Mrxvt is based on rxvt which we recently removed due to the fact that > upstream is dead and that thee code is vulnerable to CVE-2017-7483 [1]. > > Mrxvt is vulnerable as well, and latest release is from 2008. > > Comments? OK to remove? > > [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7483 ok bentley@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: czark...@cvs.openbsd.org2017/06/23 18:25:12 Modified files: net: Makefile Log message: +telegram-purple
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: czark...@cvs.openbsd.org2017/06/23 18:20:18 Log message: import telegram-purple Telegram-purple is a libpurple protocol plugin that adds support for the Telegram messenger. OK, feedback and tweaks bcallah@, sthen@ Status: Vendor Tag: czarkoff Release Tags: czarkoff_20170624 N ports/net/telegram-purple/Makefile N ports/net/telegram-purple/distinfo N ports/net/telegram-purple/patches/patch-Makefile_in N ports/net/telegram-purple/patches/patch-tgl_Makefile_in N ports/net/telegram-purple/pkg/DESCR N ports/net/telegram-purple/pkg/PLIST No conflicts created by this import
Re: Remove x11/mrxvt?
On Sat, 24 Jun 2017 00:15:17 +0200, Frederic Cambuswrote: > Hi ports@, > > Mrxvt is based on rxvt which we recently removed due to the fact that > upstream is dead and that thee code is vulnerable to CVE-2017-7483 > [1]. > > Mrxvt is vulnerable as well, and latest release is from 2008. > > Comments? OK to remove? > > [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7483 > on our top secret chan: 2017-06-06 21:31:04 danjwhile removing rxvt I saw mrxvt 2017-06-06 21:31:18 danjHOMEPAGE is http://materm.sourceforge.net 2017-06-06 21:31:28 danjshould it get removed too? :3 2017-06-06 21:32:38 danjthere's dust everywhere :) so ok with me (I can do the proxy and give you another ok from someone else if needed :3)
update attempt on print/poppler
Hi, I'm currently running an update bulk build with the diff for print/poppler below. Please ignore the commented COMPILER_LANGS entry for now (everything in poppler is c++, anyways). Apart from general fallout I'll see tomorrow, I'm not sure how to deal with some WANTLIB entries. Here's the output of port-lib-depends-check on amd64 (with gcc as the default compiler in base): poppler-0.56.0(print/poppler,-main): Missing lib: estdc++.17 (/usr/local/lib/libpoppler.so.44.0) (NOT REACHABLE) poppler-qt4-0.56.0(print/poppler,-qt4): Missing: estdc++.17 from gcc-libs-4.9.4p5 (/usr/local/lib/libpoppler-qt4.so.20.1) Missing: stdc++.57 (/usr/local/lib/libpoppler-qt4.so.20.1) (system lib) WANTLIB += estdc++ ${LIBCXX} poppler-utils-0.56.0(print/poppler,-utils): Missing lib: estdc++.17 (/usr/local/bin/pdfunite) (NOT REACHABLE) *** Error 1 in target 'port-lib-depends-check' (ignored) So, how do I add the correct libc++ added to WANTLIB-*? And, more important: what sould be done about qt4? Set COMPILER=gcc there ,too? Mixing base libstdc++ and ports libestdc++ doesn't look correct. Ciao, Kili Index: Makefile === RCS file: /cvs/ports/print/poppler/Makefile,v retrieving revision 1.122 diff -u -p -r1.122 Makefile --- Makefile13 May 2017 17:40:26 - 1.122 +++ Makefile23 Jun 2017 21:15:15 - @@ -5,7 +5,7 @@ COMMENT-qt4=qt4 interface to PDF render COMMENT-qt5= Qt5 interface to PDF rendering library COMMENT-utils= PDF conversion tools and utilities -V= 0.52.0 +V= 0.56.0 DISTNAME= poppler-$V CATEGORIES=print PKGNAME-main= poppler-$V @@ -15,10 +15,10 @@ PKGNAME-qt5=poppler-qt5-$V EXTRACT_SUFX= .tar.xz -SHARED_LIBS += poppler 43.1 # 66.0 -SHARED_LIBS += poppler-glib 16.0 # 16.0 +SHARED_LIBS += poppler 44.0 # 67.0 +SHARED_LIBS += poppler-glib 17.0 # 17.0 SHARED_LIBS += poppler-qt4 20.1 # 15.0 -SHARED_LIBS += poppler-qt5 3.1 # 10.0 +SHARED_LIBS += poppler-qt5 4.0 # 11.0 SHARED_LIBS += poppler-cpp 8.0 # 3.0 HOMEPAGE= http://poppler.freedesktop.org/ @@ -41,6 +41,10 @@ MULTI_PACKAGES=-main -qt4 -qt5 -utils .include +# c++-11 +COMPILER= gcc +# COMPILER_LANGS= c++ + cWANTLIB= expat freetype fontconfig jpeg m pthread tiff z .if ${BUILD_PACKAGES:M-qt4} @@ -81,12 +85,12 @@ LIB_DEPENDS-utils= print/poppler WANTLIB-main= ${cWANTLIB} Xext ffi gio-2.0 glib-2.0 gmodule-2.0 \ gobject-2.0 pixman-1 openjp2 X11 Xrender cairo pcre \ png pthread-stubs xcb xcb-render lcms2 xcb-shm \ - iconv intl ${LIBCXX} + iconv intl WANTLIB-qt4=${cWANTLIB} ${MODQT4_WANTLIB} ICE QtCore QtGui QtXml \ SM X11 Xext Xi Xinerama Xrender ffi glib-2.0 \ gobject-2.0 gthread-2.0 iconv intl lcms2 openjp2 \ - png poppler pcre pthread-stubs ${LIBCXX} xcb + png poppler pcre pthread-stubs xcb WANTLIB-qt5= ${cWANTLIB} $(LIBECXX) \ GL Qt5Core Qt5Gui Qt5Widgets Qt5Xml X11 X11-xcb \ @@ -96,7 +100,7 @@ WANTLIB-qt5= ${cWANTLIB} $(LIBECXX) \ pcre16 png poppler pthread-stubs xcb xcb-dri2 xcb-glx WANTLIB-utils= X11 Xext Xrender c cairo fontconfig lcms2 m pixman-1 \ - png pthread-stubs ${LIBCXX} xcb xcb-render xcb-shm openjp2 \ + png pthread-stubs xcb xcb-render xcb-shm openjp2 \ poppler z ${cWANTLIB} CONFIGURE_STYLE=autoconf @@ -114,19 +118,5 @@ CONFIGURE_ENV+= CPPFLAGS="-I${X11BASE}/i ac_cv_prog_MOCQT4=${MODQT4_MOC} USE_GMAKE= Yes - -MAIN_CC= /usr/bin/cc -MAIN_CXX= /usr/bin/c++ -.if "${USE_CCACHE:L}" == "yes" -MAIN_CC:= ccache ${MAIN_CC} -MAIN_CXX:= ccache ${MAIN_CXX} -.endif - -post-configure: - find ${WRKBUILD} -name Makefile \! -path '*/qt5/*' -print0 | xargs -0 \ - perl -pi -e 's,^CC = \S+,override CC = ${MAIN_CC},;' \ --e's,^CPP = \S+,override CPP = ${MAIN_CC},;' \ --e's,^CXX = \S+,override CXX = ${MAIN_CXX},;' \ --e 's,^CXXCPP = \S+,override CXXCPP = ${MAIN_CXX},;' .include Index: distinfo === RCS file: /cvs/ports/print/poppler/distinfo,v retrieving revision 1.63 diff -u -p -r1.63 distinfo --- distinfo26 Mar 2017 19:51:36 - 1.63 +++ distinfo23 Jun 2017 19:36:50 - @@ -1,2 +1,2 @@ -SHA256 (poppler-0.52.0.tar.xz) = UotmFziDn5ol9uWA/NLV2wB+ChlIWAxkifAGJ5jKGZI= -SIZE (poppler-0.52.0.tar.xz) = 1692144 +SHA256 (poppler-0.56.0.tar.xz) = hp2635ntiC53asvbwGaJ2KgYcqKWNECx6FFs16JXcXM= +SIZE (poppler-0.56.0.tar.xz) = 1701488 Index: patches/patch-poppler_XRef_cc === RCS file:
Remove x11/mrxvt?
Hi ports@, Mrxvt is based on rxvt which we recently removed due to the fact that upstream is dead and that thee code is vulnerable to CVE-2017-7483 [1]. Mrxvt is vulnerable as well, and latest release is from 2008. Comments? OK to remove? [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7483
LibrePCB build and port.
Hello ports, hope i am not writing at the wrong place. i’m trying to compile https://github.com/LibrePCB/LibrePCB in order to make a basic port file as a first baby step before going for porting other Qt-based applications. i’m encountering issues with qmake-qt5 build that seems specific to OpenBSD. I am running -current . Is there anyone familiar porting Qt-based software i could ask some questions? i’m feeling stuck with silly issues . Best regards, Jerome
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: czark...@cvs.openbsd.org2017/06/23 13:50:42 Modified files: www: Makefile www/surf : Makefile www/surf/pkg : PLIST devel/quirks : Makefile devel/quirks/files: Quirks.pm Removed files: www/surf2 : Makefile distinfo www/surf2/patches: patch-Makefile patch-config_def_h patch-config_mk patch-surf_1 www/surf2/pkg : DESCR PLIST Log message: Remove www/surf2 in favor of www/surf Prodded by jung@
Update to duplicity-0.7.13.1 with 2 new python ports
Hi, This duplicity update has a new RDEP (py-fasteners) which itself needs another new RDEP (py-monotonic). Changelog is mainly bugfixes and 0.7.13.1 is a bugfix release for Mac according to changelog. Testing the whole is appreciated if you can. Comments? Nitpick over pkg/DESCR? OK? Cheers, Daniel py-fasteners.tgz Description: application/compressed-tar py-monotonic.tgz Description: application/compressed-tar Index: Makefile === RCS file: /cvs/ports/sysutils/duplicity/Makefile,v retrieving revision 1.42 diff -u -p -r1.42 Makefile --- Makefile 19 May 2017 02:33:27 - 1.42 +++ Makefile 23 Jun 2017 19:22:11 - @@ -5,9 +5,8 @@ COMMENT = encrypted backup using rsync algorithm -MODPY_EGG_VERSION = 0.7.12 +MODPY_EGG_VERSION = 0.7.13.1 DISTNAME = duplicity-${MODPY_EGG_VERSION} -REVISION = 0 CATEGORIES = sysutils @@ -28,7 +27,8 @@ WANTLIB += pthread rsync ${MODPY_WANTLIB LIB_DEPENDS += net/librsync \ ${MODPY_LIB_DEPENDS} -RUN_DEPENDS += devel/py-pexpect \ +RUN_DEPENDS += devel/py-fasteners \ + devel/py-pexpect \ net/ncftp \ net/py-boto \ gnupg-<2:security/gnupg \ Index: distinfo === RCS file: /cvs/ports/sysutils/duplicity/distinfo,v retrieving revision 1.24 diff -u -p -r1.24 distinfo --- distinfo 14 May 2017 18:37:08 - 1.24 +++ distinfo 23 Jun 2017 19:22:11 - @@ -1,2 +1,2 @@ -SHA256 (duplicity-0.7.12.tar.gz) = EcutRKkIka8b+eKUJgunwhoWYMzTqyxuc2unSsXPD+Y= -SIZE (duplicity-0.7.12.tar.gz) = 1552442 +SHA256 (duplicity-0.7.13.1.tar.gz) = rbhmj7EOCw+Ry3f3WNAsAr9cAubEg1kEqCy9q220vvI= +SIZE (duplicity-0.7.13.1.tar.gz) = 1553736 Index: patches/patch-bin_duplicity === RCS file: /cvs/ports/sysutils/duplicity/patches/patch-bin_duplicity,v retrieving revision 1.9 diff -u -p -r1.9 patch-bin_duplicity --- patches/patch-bin_duplicity 9 Aug 2016 11:16:53 - 1.9 +++ patches/patch-bin_duplicity 23 Jun 2017 19:22:11 - @@ -1,7 +1,8 @@ $OpenBSD: patch-bin_duplicity,v 1.9 2016/08/09 11:16:53 danj Exp $ bin/duplicity.orig Sun Jul 24 18:27:49 2016 -+++ bin/duplicity Wed Aug 3 18:47:34 2016 -@@ -1268,10 +1268,12 @@ def check_resources(action): +Index: bin/duplicity +--- bin/duplicity.orig bin/duplicity +@@ -1265,10 +1265,12 @@ def check_resources(action): log.ErrorCode.get_ulimit_failed) maxopen = min([l for l in (soft, hard) if l > -1]) if maxopen < 1024: Index: pkg/PLIST === RCS file: /cvs/ports/sysutils/duplicity/pkg/PLIST,v retrieving revision 1.18 diff -u -p -r1.18 PLIST --- pkg/PLIST 3 Sep 2016 08:45:52 - 1.18 +++ pkg/PLIST 23 Jun 2017 19:22:11 - @@ -36,8 +36,6 @@ lib/python${MODPY_VERSION}/site-packages lib/python${MODPY_VERSION}/site-packages/duplicity/backends/botobackend.pyc lib/python${MODPY_VERSION}/site-packages/duplicity/backends/cfbackend.py lib/python${MODPY_VERSION}/site-packages/duplicity/backends/cfbackend.pyc -lib/python${MODPY_VERSION}/site-packages/duplicity/backends/copycombackend.py -lib/python${MODPY_VERSION}/site-packages/duplicity/backends/copycombackend.pyc lib/python${MODPY_VERSION}/site-packages/duplicity/backends/dpbxbackend.py lib/python${MODPY_VERSION}/site-packages/duplicity/backends/dpbxbackend.pyc lib/python${MODPY_VERSION}/site-packages/duplicity/backends/gdocsbackend.py
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: jas...@cvs.openbsd.org 2017/06/23 13:02:41 Modified files: x11/gnome/mutter: Makefile distinfo Log message: update to mutter-3.24.3
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: jas...@cvs.openbsd.org 2017/06/23 11:21:18 Modified files: lang/elixir: Makefile distinfo Log message: update to elixir-1.4.5
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: juan...@cvs.openbsd.org 2017/06/23 10:59:22 Modified files: lang/bacon : Makefile distinfo Log message: Update to bacon 3.5.4.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 08:54:03 Modified files: net/olsrd : Makefile Log message: Bump. -@depend devel/gettext:gettext->=0.10.38:gettext-0.19.8.1
Re: NEW archivers/geteltorito
On Fri, Jun 23, 2017 at 04:25:19PM +0200, Peter Hessler wrote: > call: geteltorito CD-image > toritoimagefile > example:geteltorito /dev/sr0 > /tmp/bootimage > > The perl-script will extract the initial/default boot image from a CD if > existant. It will not extract any of other possibly existing bootimages > that are allowed by the El Torito standard. > The imagedata are written to STDOUT all other information is written to > STDERR (eg type and size of image). > If you want to write the image to a file instead of STDOUT you can > secify the filename wanted on the commandline using option -o > > > Helpful for extracting Thinkpad BIOS updates so you can put them on a > usb stick to install.. > > I put it in archivers because we're extracting data out of a larger > container. sysutils would also make sense. > > OK? Looks OK to me, just some nits regarding DESCR: I would put these lines at the end of DESCR, not on top: call: geteltorito CD-image > toritoimagefile example:geteltorito /dev/sr0 > /tmp/bootimage And change /dev/sr0 to a device that can be used on OpenBSD. I suggest to rephrase: The perl-script will extract ... to this: geteltorito will extract ...
NEW archivers/geteltorito
call: geteltorito CD-image > toritoimagefile example:geteltorito /dev/sr0 > /tmp/bootimage The perl-script will extract the initial/default boot image from a CD if existant. It will not extract any of other possibly existing bootimages that are allowed by the El Torito standard. The imagedata are written to STDOUT all other information is written to STDERR (eg type and size of image). If you want to write the image to a file instead of STDOUT you can secify the filename wanted on the commandline using option -o Helpful for extracting Thinkpad BIOS updates so you can put them on a usb stick to install.. I put it in archivers because we're extracting data out of a larger container. sysutils would also make sense. OK? -- "... an experienced, industrious, ambitious, and often quite often picturesque liar." -- Mark Twain geteltorito.tgz Description: application/tar-gz
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 07:39:48 Modified files: x11/gtk3mm : Makefile distinfo Log message: Update to gtk3mm-3.22.1.
Re: New port: net/telegram-purple
On 6/23/2017 7:24 AM, Dmitrij D. Czarkoff wrote: > Brian Callahanwrote: > >> Run tested it on amd64, works fine. >> Why not do this though: >> >> USE_GMAKE = Yes >> MAKE_FLAGS =CC="${CC}" >> CONFIGURE_STYLE = gnu >> CONFIGURE_ENV = CFLAGS="${CFLAGS} -I${LOCALBASE}/include" \ >>LDFLAGS="${LDFLAGS} -L${LOCALBASE}/lib" >> >> Then it'll de-hardcode gcc, and you can remove those extra CFLAGS+= and >> LDFLAGS= lines. > Basically I define CFLAGS separately because they are also passed to > MAKE_ENV, and then defining LDFLAGS there seems more aestetically > pleasant to me. This approach does not provide any actual benefits in > this case though, so I don't really want to insist on it. > > Regarding MAKE_FLAGS addition: I'd rather avoid unnecessarily polluting > the environment, so patching Makefile.in seems more appropriate to me. > And I prefer to avoid writing patches, but I'm not gonna insist on it either :) That new version is ok by me too for import. ~Brian
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 07:11:32 Modified files: sysutils/awscli: Makefile distinfo Log message: Update to awscli-1.11.111.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 07:11:17 Modified files: net/py-botocore: Makefile distinfo net/py-botocore/pkg: PLIST Log message: Update to py-botocore-1.5.74.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 06:59:37 Modified files: sysutils/salt : Makefile distinfo sysutils/salt/pkg: PLIST Log message: Update to salt-2016.11.6.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 06:49:55 Modified files: devel/glib2mm : Makefile distinfo devel/glib2mm/pkg: PLIST Log message: Update to glib2mm-2.52.0.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: r...@cvs.openbsd.org2017/06/23 06:46:45 Modified files: sysutils : Makefile Log message: add waagent, OK sthen@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: r...@cvs.openbsd.org2017/06/23 06:37:09 Log message: The Microsoft Azure Linux Agent (waagent) manages Linux & BSD provisioning, and VM interaction with the Azure Fabric Controller. OpenBSD is supported by upstream since version 2.2.13. OK sthen@ Status: Vendor Tag: reyk Release Tags: reyk_20170623 N ports/sysutils/waagent/Makefile N ports/sysutils/waagent/distinfo N ports/sysutils/waagent/pkg/DESCR N ports/sysutils/waagent/pkg/PLIST N ports/sysutils/waagent/pkg/waagent.rc N ports/sysutils/waagent/patches/patch-azurelinuxagent_common_conf_py N ports/sysutils/waagent/patches/patch-azurelinuxagent_ga_update_py N ports/sysutils/waagent/patches/patch-config_openbsd_waagent_conf N ports/sysutils/waagent/patches/patch-config_waagent_conf N ports/sysutils/waagent/patches/patch-azurelinuxagent_common_osutil_openbsd_py No conflicts created by this import
Re: NEW: databases/citus
On 06/23/17 13:34, Stuart Henderson wrote: > On 2017/06/23 13:23, Martijn Rijkeboer wrote: >> Hi, >> >> Attached is a new port, databases/citus. Citus is an extension that adds >> horizontally scale to PostgreSQL. >> >> --- >> pkg/DESCR: >> Citus horizontally scales PostgreSQL across multiple machines using >> sharding and replication. Its query engine parallelizes incoming SQL >> queries across these servers to enable human real-time (less than a >> second) responses on large datasets. >> >> Citus extends the underlying database rather than forking it, which >> gives developers and enterprises the power and familiarity of a >> traditional relational database. As an extension, Citus supports new >> PostgreSQL releases, allowing users to benefit from new features while >> maintaining compatibility with existing PostgreSQL tools. >> --- >> >> OK? >> >> >> Kind regards, >> >> >> Martijn Rijkeboer > > : COMMENT = extension to horizontally scale PostgreSQL > : DISTNAME = citus-6.2.2 > : GH_ACCOUNT =citusdata > : GH_PROJECT =citus > : GH_TAGNAME =v6.2.2 > > remove the DISTNAME, this is the default with those GH_* variables anyway. > > : #SHARED_LIBS = ??? > > remove > > : BUILD_DEPENDS = databases/postgresql,-server > : RUN_DEPENDS = databases/postgresql,-server > > this should be: > > LIB_DEPENDS = databases/postgresql > RUN_DEPENDS = databases/postgresql,-server Here's an updated version that includes your comments. OK? Kind regards, Martijn Rijkeboer citus-6.2.2-take2.tgz Description: application/compressed-tar
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2017/06/23 05:40:36 Modified files: net/libmaxminddb: Makefile distinfo Added files: net/libmaxminddb/pkg: DESCR-asn PLIST-asn Log message: Update a few things in libmaxminddb: - Update the geolite2 maintainer target to cope with new upstream packaging scheme, and also fetch the ASN database - Add a subpackage for the ASN database - Update GeoLite2 databases to latest version OK sthen@
Re: NEW: databases/citus
On 2017/06/23 13:23, Martijn Rijkeboer wrote: > Hi, > > Attached is a new port, databases/citus. Citus is an extension that adds > horizontally scale to PostgreSQL. > > --- > pkg/DESCR: > Citus horizontally scales PostgreSQL across multiple machines using > sharding and replication. Its query engine parallelizes incoming SQL > queries across these servers to enable human real-time (less than a > second) responses on large datasets. > > Citus extends the underlying database rather than forking it, which > gives developers and enterprises the power and familiarity of a > traditional relational database. As an extension, Citus supports new > PostgreSQL releases, allowing users to benefit from new features while > maintaining compatibility with existing PostgreSQL tools. > --- > > OK? > > > Kind regards, > > > Martijn Rijkeboer : COMMENT = extension to horizontally scale PostgreSQL : DISTNAME = citus-6.2.2 : GH_ACCOUNT =citusdata : GH_PROJECT =citus : GH_TAGNAME =v6.2.2 remove the DISTNAME, this is the default with those GH_* variables anyway. : #SHARED_LIBS = ??? remove : BUILD_DEPENDS = databases/postgresql,-server : RUN_DEPENDS = databases/postgresql,-server this should be: LIB_DEPENDS = databases/postgresql RUN_DEPENDS = databases/postgresql,-server
Re: New port: net/telegram-purple
Brian Callahanwrote: >Run tested it on amd64, works fine. >Why not do this though: > >USE_GMAKE = Yes >MAKE_FLAGS =CC="${CC}" >CONFIGURE_STYLE = gnu >CONFIGURE_ENV = CFLAGS="${CFLAGS} -I${LOCALBASE}/include" \ >LDFLAGS="${LDFLAGS} -L${LOCALBASE}/lib" > >Then it'll de-hardcode gcc, and you can remove those extra CFLAGS+= and >LDFLAGS= lines. Basically I define CFLAGS separately because they are also passed to MAKE_ENV, and then defining LDFLAGS there seems more aestetically pleasant to me. This approach does not provide any actual benefits in this case though, so I don't really want to insist on it. Regarding MAKE_FLAGS addition: I'd rather avoid unnecessarily polluting the environment, so patching Makefile.in seems more appropriate to me.
NEW: databases/citus
Hi, Attached is a new port, databases/citus. Citus is an extension that adds horizontally scale to PostgreSQL. --- pkg/DESCR: Citus horizontally scales PostgreSQL across multiple machines using sharding and replication. Its query engine parallelizes incoming SQL queries across these servers to enable human real-time (less than a second) responses on large datasets. Citus extends the underlying database rather than forking it, which gives developers and enterprises the power and familiarity of a traditional relational database. As an extension, Citus supports new PostgreSQL releases, allowing users to benefit from new features while maintaining compatibility with existing PostgreSQL tools. --- OK? Kind regards, Martijn Rijkeboer citus-6.2.2.tgz Description: application/compressed-tar
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2017/06/23 04:58:32 Modified files: security/lastpass-cli: Makefile distinfo security/lastpass-cli/patches: patch-CMakeLists_txt Log message: update to lastpass-cli 1.2.0, from maintainer Björn Ketelaars
Re: [PATCH] net/libmaxminddb
On 2017/06/08 23:19, Frederic Cambus wrote: > Here is a diff to update a few things in the net/libmaxminddb port: > > - Update the geolite2 maintainer target to cope with new upstream > packaging scheme, and also fetch the ASN database > - Add a subpackage for the ASN database > - Update GeoLite2 databases to latest version OK but I have some nitpicking comments inline :) > Index: Makefile > === > RCS file: /cvs/ports/net/libmaxminddb/Makefile,v > retrieving revision 1.13 > diff -u -p -r1.13 Makefile > --- Makefile 4 Jun 2017 10:57:59 - 1.13 > +++ Makefile 8 Jun 2017 14:01:11 - > @@ -3,16 +3,18 @@ > COMMENT-main = library for MaxMind GeoIP2/GeoLite2 IP geolocation > databases > COMMENT-db = GeoIP2 GeoLite2 database: IPv4/v6 address to country > COMMENT-city = GeoIP2 GeoLite2 database: IPv4/v6 address to city > +COMMENT-asn =GeoIP2 GeoLite2 database: IPv4/v6 address to AS number > > V = 1.2.1 > -D = 20170503 > +D = 20170608 > DISTNAME = libmaxminddb-${V} > PKGNAME-main = libmaxminddb-${V} > PKGNAME-db = geolite2-country-${D} > PKGNAME-city = geolite2-city-${D} > +PKGNAME-asn =geolite2-asn-${D} > DISTFILES = ${DISTNAME}${EXTRACT_SUFX} \ > geolite2-data-$D.tar.xz:0 > -REVISION = 0 > +REVISION-main = 0 > > SHARED_LIBS += maxminddb 0.0 # 0.7 > > @@ -31,7 +33,7 @@ WANTLIB-main += c m > MASTER_SITES = ${HOMEPAGE}/releases/download/${V}/ > MASTER_SITES0 = https://www.distfiles.pl/ > > -MULTI_PACKAGES = -main -db -city > +MULTI_PACKAGES = -main -db -city -asn > RUN_DEPENDS-main = net/libmaxminddb,-db > > TEST_DEPENDS = devel/p5-IPC-Run3 > @@ -56,13 +58,16 @@ geolite2: > echo "see https://www.maxmind.com and > https://dev.maxmind.com/geoip/geoip2/geolite2/.; >> README; \ > echo "Distributed under Creative Commons Attribution-ShareAlike 4.0 > International License." >> README; \ > echo "Created at `date -z UTC` and intended for OS packaging purposes." > >> README; \ > - ftp > https://geolite.maxmind.com/download/geoip/database/GeoLite2-{Country,City}.{md5,mmdb.gz}; > \ > - gunzip *gz; \ > - for file in GeoLite2-Country GeoLite2-City; do \ > - if [ "`md5 -q $$file.mmdb`" != "`cat $$file.md5`" ]; then \ > - echo "ERROR: $$file.mmdb is corrupt"; \ > + ftp > https://geolite.maxmind.com/download/geoip/database/GeoLite2-{Country,City,ASN}.{tar.gz,tar.gz.md5}; > \ A quick glance at this makes it look like you fetch .tar.gz twice, so I'd slightly prefer GeoLite2-{Country,City,ASN}.tar.gz{,.md5} > + for file in GeoLite2-Country GeoLite2-City GeoLite2-ASN; do \ > + if [ "`md5 -q $$file.tar.gz`" != "`cat $$file.tar.gz.md5`" ]; > then \ > + echo "ERROR: $$file.tar.gz is corrupt"; \ > exit; \ > fi; \ > + tar xfz $$file.tar.gz; \ > + done; \ > + for file in `find * -type f | grep mmdb`; do \ > + mv $$file .; \ > done; \ could just do "mv */*mmdb ." and save some execs.
Re: New port: net/telegram-purple
Stuart Hendersonwrote: >On 2017/06/22 18:11, Dmitrij D. Czarkoff wrote: >> "Dmitrij D. Czarkoff" wrote: >> >>>The attached port contains libpurple protocol plugin that adds support >>>for the Telegram messenger to net/pidgin. >>> >>>OK to import? >> >> ping > >Build-testing only (I'm not going to run pidgin to try it \ >out at runtime), >there are parts where it hardcodes gcc. Otherwise looks ok. Sorry, I did not notice that. The updated port fixes that. Basically I patch Makefile to pass CC to nested configure invocation. telegram-purple-1.3.1.tgz Description: application/gzip
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2017/06/23 04:51:25 Modified files: audio/libmikmod: Makefile distinfo Log message: Update libmikmod to 3.3.11.1. Thanks Ozkan Sezer for the heads up.
Re: New port: net/telegram-purple
Jakub Skrzypnikwrote: >I would like to ask about something different - how tightly is that >telegram support tied to GUI libraries? Some of these libpurple-based >transports for IM protocols are tied up to use with Pidgin/Adium, >completely ignoring the fact that libpurple can be used by many other >applications. > >The problem itself is that I would like to use Bitlbee with libpurple >for XMPP, GG, Facebook and Telegram if it gets merged, but I'm a bit >afraid about pushing the whole GUI stack as a dependency tail of >libpurple and/or these transports, while libpurple itself can actually >work without X. This port does not depend on any X11 stuff, and it is known to work with finch (console version of pidgin). For all I know there is an open issue about a user being constantly signed out from telegram on Bitlbee¹, though I am not sure whether it is an issue with particular setup, or a defect in telegram-purple. You can actually build a port and test it. ¹ https://github.com/majn/telegram-purple/issues/392
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2017/06/23 01:29:17 Modified files: devel/glib2: Makefile distinfo devel/glib2/pkg: PLIST Log message: Update to glib2-2.52.3.