Re: tedu lang/ghc?
On Wed, May 08, 2013 at 08:00:42AM +0200, Dawe wrote: > To lower the impact of ghc we could remove all hs-ports that don't need > patching > and work out of the box with cabal. The biggest current problem is that there'll be a flag day when we switch to 64 bit time_t. After this day, neiter an installed ghc nor the ghc bootstrapping binaries will work any longer. I've prepared a bootstrapping sequence starting with ghc-6.6 (bootstrapping from .hc files), going through several ghc versions up to 7.4, but this still not working. After all the years dealing with all this ghc bullshit (broken bootstrapping, non-deterministic symbol names, incompatible changes with every release) I'm seriously loosing interest. Ciao, Kili
Re: tedu lang/ghc?
On May 07, 2013 23:50, Matthias Kilian wrote: > Spoiler: I'm not talking about Haskell but about ghc here. You mean keeping hugs and remove everything else? Because I don't see how hugs could build all the packages that make use of haskell2010 and all the ghc-extensions. The utrecht compiler isn't an option as well, because it needs ghc to bootstrap and even then doesn't support all ghc-extensions. To lower the impact of ghc we could remove all hs-ports that don't need patching and work out of the box with cabal. Or we could unhook all hs-ports and only keep the haskell-stuff hooked, that people need to build their desired hs-ports. If something breaks, it would be their problem to rebuild the hs-ports that would otherwise get a bump. I hope we can find a solution without removing ghc because that would force me to switch to another OS entirely :( (starting my thesis next week using haskell) > > I'd like to remove lang/ghc from the ports tree, because it's fucked > up beyond repair: > > - configure runs ghc-pwd (instead of just pwd) to determine the current > working directory. ghc-pwd is a program written in Haskell. In the > past, when ghc-pwd appeared, configure first compiled that ghc-pwd > program, which wouldn't work unless you already have a working > Haskell compiler installed. > > - after replacing all occurrences of ghc-pwd by /bin/pwd, the build > fails because it runs ghc-stage2 from the bootstrapper. (Note > that binaries for ghc-pwd as well as ghc-stage2 and much more are > included in the ghc sources and/or the bootstrapper for this > purpose). > > - bootstrapping without a pre-installed ghc still doesn't work, and > upstream doesn't careA > > - the ghc compiler is not deterministic, because function names (in > hs-libraries) depend on what's already built. So if you start a > build of ghc, interrupt it and restart it, you may end up with binary > incompatible libraries to an uninterrupted build. This is also the > reason for all those package bumps we do on hs-* ports. > > - with every new major ghc release, interfaces break. For example, last > summer I had to fix various "Num doesn't imply EQ" issues as > well as a lot of general typesystem issues. Imagine annual changes > to the C programming language that require not only recompiliton > but rewrites! > > So let's get rid of this crap. > > Ciao, > Kili >
Re: tedu lang/ghc?
Even though I am using GHC almost daily, I agree it is a pile of junk. I still wonder how you are going to manage to keep Haskell but not having GHC anymore. As far as I know there are only two Haskell compilers actively developed except for GHC: UHC and JHC. The other implementations are not maintained anymore. These two will probably not work well with xmonad and xmobar (I am a user of both also). Hugs (already in ports) is not a good alternative as it is not even maintained upstream anymore. Sometimes piles of junk are kept in a system because the alternatives have not caught up. But on the other hand, it is your spare time and you do with it as you want :) On 05/08/13 00:50, Matthias Kilian wrote: Spoiler: I'm not talking about Haskell but about ghc here. I'd like to remove lang/ghc from the ports tree, because it's fucked up beyond repair: - configure runs ghc-pwd (instead of just pwd) to determine the current working directory. ghc-pwd is a program written in Haskell. In the past, when ghc-pwd appeared, configure first compiled that ghc-pwd program, which wouldn't work unless you already have a working Haskell compiler installed. - after replacing all occurrences of ghc-pwd by /bin/pwd, the build fails because it runs ghc-stage2 from the bootstrapper. (Note that binaries for ghc-pwd as well as ghc-stage2 and much more are included in the ghc sources and/or the bootstrapper for this purpose). - bootstrapping without a pre-installed ghc still doesn't work, and upstream doesn't careA - the ghc compiler is not deterministic, because function names (in hs-libraries) depend on what's already built. So if you start a build of ghc, interrupt it and restart it, you may end up with binary incompatible libraries to an uninterrupted build. This is also the reason for all those package bumps we do on hs-* ports. - with every new major ghc release, interfaces break. For example, last summer I had to fix various "Num doesn't imply EQ" issues as well as a lot of general typesystem issues. Imagine annual changes to the C programming language that require not only recompiliton but rewrites! So let's get rid of this crap. Ciao, Kili
Re: enabling jit in devel/pcre
up
2013/5/4 Илья Шипицин :
> hmm, next patch edition.
>
> --- devel/pcre/Makefile.origSat May 4 14:57:28 2013
> +++ devel/pcre/Makefile Sat May 4 12:17:52 2013
> @@ -30,11 +30,18 @@
> USE_LIBTOOL= Yes
> USE_GROFF =Yes
> CONFIGURE_STYLE= gnu
> +
> CONFIGURE_ARGS=${CONFIGURE_SHARED} \
> --enable-pcre8 \
> --enable-pcre16 \
> --enable-utf \
> - --enable-unicode-properties
> + --enable-unicode-properties
> +
> +.if ${MACHINE_ARCH} == "amd64" || ${MACHINE_ARCH} == "i386" ||
> ${MACHINE_ARCH} == "powerpc" || ${MACHINE_ARCH} == "powerpc64" ||
> ${MACHINE_ARCH} == "mips64" || ${MACHINE_ARCH} == "mips64el" ||
> ${MACHINE_ARCH} == "arm"
> +CFLAGS+=-lpthread
> +CONFIGURE_ARGS+=--enable-jit
> +.endif
> +
>
> # XXX compiler bugs
> .if ${MACHINE_ARCH} == "vax"
>
> 2013/5/4 Matthias Kilian :
>> On Sat, May 04, 2013 at 01:02:43PM +0600, ??? wrote:
>>> we are using nginx with pcre_jit feature. however, devel/pcre comes
>>> without jit enabled. I suggest to compile devel/pcre with jit by
>>> default.
>>
>> From the README:
>>
>> This support is available only for certain hardware
>> architectures. If you try to enable it on an unsupported
>> architecture, there will be a compile time error.
>>
>> Did you check wether it works on all architectures OpenBSD runs on?
>>
>> Ciao,
>> Kili
Re: UPDATE: devel/fox 1.6.37 => 1.6.49
On 5/4/2013 7:31 PM, Brian Callahan wrote: Hi ports -- Here's an update for devel/fox to 1.6.49 Needed for a new port. Works for me on amd64, loongson, and macppc. OK? ~Brian Ping. Our port is over 3 years old, it's really time for an update. ~Brian
[PATCH] metaauto should pull pkg.m4 from pkgconfig-0.27.1
Hey,
OpenBSD's pkg-config reports its version as 0.27.1, so it would make
sure to have metaauto pull pkg.m4 from freedesktop.org's
pkgconfig-027.1. This adds a few new macros that newer autoconf projects
use.
Thanks,
WIlliam Orr
? metaauto-pkgconfig-0.27.1.patch
Index: Makefile
===
RCS file: /cvs/ports/devel/metaauto/Makefile,v
retrieving revision 1.17
diff -u -r1.17 Makefile
--- Makefile11 Mar 2013 10:50:11 - 1.17
+++ Makefile7 May 2013 23:06:22 -
@@ -3,9 +3,10 @@
COMMENT = wrapper for gnu auto*
VERSION = 1.0
+REVISION = 1
DISTNAME = metaauto-${VERSION}
CATEGORIES = devel
-DISTFILES =pkg-config-0.21.tar.gz
+DISTFILES =pkg-config-0.27.1.tar.gz
MAINTAINER = Marc Espie
@@ -35,6 +36,6 @@
${INSTALL_SCRIPT} ${WRKBUILD}/$i ${PREFIX}/bin
.endfor
${INSTALL_DATA_DIR} ${PREFIX}/share/aclocal
- ${INSTALL_DATA} ${WRKDIR}/pkg-config-0.21/pkg.m4 ${PREFIX}/share/aclocal
+ ${INSTALL_DATA} ${WRKDIR}/pkg-config-0.27.1/pkg.m4
${PREFIX}/share/aclocal
.include
Index: distinfo
===
RCS file: /cvs/ports/devel/metaauto/distinfo,v
retrieving revision 1.3
diff -u -r1.3 distinfo
--- distinfo5 Apr 2007 15:37:56 - 1.3
+++ distinfo7 May 2013 23:06:22 -
@@ -1,5 +1,2 @@
-MD5 (pkg-config-0.21.tar.gz) = R29F+rFQSqxml6p3hfCrkQ==
-RMD160 (pkg-config-0.21.tar.gz) = bUjkSaPO21dsD1SwiCW+araE2VU=
-SHA1 (pkg-config-0.21.tar.gz) = slCLqEBMrUbsQvb1jLykOuWdcV8=
-SHA256 (pkg-config-0.21.tar.gz) = 6IMfQ8gSal2jJQKQHFjMGjnv/gRd0pMubic8yNZ/Yz8=
-SIZE (pkg-config-0.21.tar.gz) = 998420
+SHA256 (pkg-config-0.27.1.tar.gz) =
T2PQ3zA1EBsSlJJQ2lIxr0njw6/Nj7GFVPp8PLktjBc=
+SIZE (pkg-config-0.27.1.tar.gz) = 1908265
update: trojita-0.3.93
Update to Trojita 0.3.93. Take maintainership (should have just done it
in the first place). Patches no longer needed so be sure to apply with
-E. Tested on amd64. oks?
--
James Turner
Index: Makefile
===
RCS file: /cvs/ports/mail/trojita/Makefile,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 Makefile
--- Makefile25 Apr 2013 22:58:42 - 1.1.1.1
+++ Makefile7 May 2013 23:57:14 -
@@ -2,8 +2,10 @@
COMMENT = fast Qt IMAP e-mail client
-DISTNAME = trojita-0.3.92
+DISTNAME = trojita-0.3.93
CATEGORIES = mail x11
+
+MAINTAINER = James Turner
HOMEPAGE = http://trojita.flaska.net/
MASTER_SITES = ${MASTER_SITE_SOURCEFORGE:=trojita/}
Index: distinfo
===
RCS file: /cvs/ports/mail/trojita/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 distinfo
--- distinfo25 Apr 2013 22:58:42 - 1.1.1.1
+++ distinfo7 May 2013 23:57:14 -
@@ -1,2 +1,2 @@
-SHA256 (trojita-0.3.92.tar.bz2) = dog/8B7d6qEmpRWYEoUC/WuNkQjdGm6P4kO9aS5Xwq4=
-SIZE (trojita-0.3.92.tar.bz2) = 648920
+SHA256 (trojita-0.3.93.tar.bz2) = Ylv3/e0/AKRfb06v5QT6PiDiN2MgcvfkeUnQoTOSdOQ=
+SIZE (trojita-0.3.93.tar.bz2) = 966396
Index: patches/patch-src_po2qm_prf
===
RCS file: patches/patch-src_po2qm_prf
diff -N patches/patch-src_po2qm_prf
--- patches/patch-src_po2qm_prf 25 Apr 2013 22:58:42 - 1.1.1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,28 +0,0 @@
-$OpenBSD: patch-src_po2qm_prf,v 1.1.1.1 2013/04/25 22:58:42 jturner Exp $
-
-commit 5a8c487a8ae3bdde44c580d6c1e22354009b0984
-Author: James Turner
-Date: Fri Apr 19 10:36:20 2013 +0200
-
src/po2qm.prf.orig Wed Feb 27 17:29:55 2013
-+++ src/po2qm.prf Fri Apr 19 18:58:50 2013
-@@ -10,8 +10,18 @@ isEmpty(QMAKE_LRELEASE) {
- }
- }
-
-+isEmpty(QMAKE_LCONVERT) {
-+win32|os2:QMAKE_LCONVERT = $$[QT_INSTALL_BINS]\lconvert.exe
-+else:QMAKE_LCONVERT = $$[QT_INSTALL_BINS]/lconvert
-+unix {
-+!exists($$QMAKE_LCONVERT) { QMAKE_LCONVERT = lconvert-qt4 }
-+} else {
-+!exists($$QMAKE_LCONVERT) { QMAKE_LCONVERT = lconvert }
-+}
-+}
-+
- po2qm.input = PO_FILES
- po2qm.output = locale/${QMAKE_FILE_BASE}.qm
--po2qm.commands = lconvert ${QMAKE_FILE_IN} -o ${QMAKE_FILE_BASE}.ts &&
$$QMAKE_LRELEASE -nounfinished ${QMAKE_FILE_BASE}.ts -qm
locale/${QMAKE_FILE_BASE}.qm && rm ${QMAKE_FILE_BASE}.ts
-+po2qm.commands = $$QMAKE_LCONVERT ${QMAKE_FILE_IN} -o ${QMAKE_FILE_BASE}.ts
&& $$QMAKE_LRELEASE -nounfinished ${QMAKE_FILE_BASE}.ts -qm
locale/${QMAKE_FILE_BASE}.qm && rm ${QMAKE_FILE_BASE}.ts
- po2qm.CONFIG += no_link target_predeps
- QMAKE_EXTRA_COMPILERS += po2qm
Index: pkg/PLIST
===
RCS file: /cvs/ports/mail/trojita/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 PLIST
--- pkg/PLIST 25 Apr 2013 22:58:42 - 1.1.1.1
+++ pkg/PLIST 7 May 2013 23:57:14 -
@@ -7,14 +7,18 @@ share/trojita/
share/trojita/locale/
share/trojita/locale/trojita_common_bs.qm
share/trojita/locale/trojita_common_cs.qm
+share/trojita/locale/trojita_common_da.qm
share/trojita/locale/trojita_common_de.qm
+share/trojita/locale/trojita_common_el.qm
share/trojita/locale/trojita_common_es.qm
share/trojita/locale/trojita_common_et.qm
+share/trojita/locale/trojita_common_fr.qm
share/trojita/locale/trojita_common_ga.qm
share/trojita/locale/trojita_common_gl.qm
share/trojita/locale/trojita_common_hu.qm
share/trojita/locale/trojita_common_ia.qm
share/trojita/locale/trojita_common_lt.qm
+share/trojita/locale/trojita_common_mr.qm
share/trojita/locale/trojita_common_nl.qm
share/trojita/locale/trojita_common_pl.qm
share/trojita/locale/trojita_common_pt.qm
Re: backdir: a simple little backup/versioning utility
On Mon, May 06, 2013 at 10:44:34PM -0400, Alan Corey wrote:
> On 5/6/13, James Turner wrote:
> > I took it upon myself to throw together a port. Since it's such a simple
> > tool it only needs a simple port.
> >
> > One request to the OP any chance you could add a 20130505 or a version
> > number to the tar.gz file? That way if you ever release a new version
> > the port won't break with bad checksum errors. Thanks.
> >
> > --
> > James Turner
> >
>
> Yes, there will be more versions for a little while. Maybe posting
> this was premature, but I thought the next release was a long while
> away so it was OK.
>
> I discovered today this doesn't handle spaces in filenames (I never
> use them), so I fixed that. Also it appends the date and time where
> the last period in a filename is, so file.tar.gz ends up
> file.tar_2013-05-06_1234.gz which looks a little funny. I haven't
> decided how to deal with that. Multiple periods cause a problem since
> I used strrchr('.') to place the split.
>
> If there are suggestions I might make more changes, so the checksum
> won't be stable for a little while. I don't anticipate changing it
> very often after initial beta testing, if ever.
>
> Thank you for making a port, I was looking up how to do that, but I've
> been working on something else all day. This probably needs week or
> so settling time: I've never published anything this way before. How
> do I reconnect to the project?
>
> There is now a http://ab1jx.webs.com/calcs/backdir/backdir_20135056.tar.gz
>
> Thanks again,
>
> Alan Corey, ab1jx
>
> --
> Credit is the root of all evil. - AB1JX
>
I've tweaked the port locally but will wait until things settle, then
I'll work on getting it imported.
If your interested in porting your other stuff or any other software the
Porter's Handbook [0] is a great place to start.
[0] http://www.openbsd.org/faq/ports/index.html
--
James Turner
Re: tedu lang/ghc?
On Tue, May 7, 2013 at 2:50 PM, Matthias Kilian wrote: > Spoiler: I'm not talking about Haskell but about ghc here. To ask a possibly dumb question, what are our other options for Haskell at the moment? E.g., it looks like x11/xmonad depends on lang/ghc, so does removing ghc mean removing xmonad?
tedu lang/ghc?
Spoiler: I'm not talking about Haskell but about ghc here. I'd like to remove lang/ghc from the ports tree, because it's fucked up beyond repair: - configure runs ghc-pwd (instead of just pwd) to determine the current working directory. ghc-pwd is a program written in Haskell. In the past, when ghc-pwd appeared, configure first compiled that ghc-pwd program, which wouldn't work unless you already have a working Haskell compiler installed. - after replacing all occurrences of ghc-pwd by /bin/pwd, the build fails because it runs ghc-stage2 from the bootstrapper. (Note that binaries for ghc-pwd as well as ghc-stage2 and much more are included in the ghc sources and/or the bootstrapper for this purpose). - bootstrapping without a pre-installed ghc still doesn't work, and upstream doesn't careA - the ghc compiler is not deterministic, because function names (in hs-libraries) depend on what's already built. So if you start a build of ghc, interrupt it and restart it, you may end up with binary incompatible libraries to an uninterrupted build. This is also the reason for all those package bumps we do on hs-* ports. - with every new major ghc release, interfaces break. For example, last summer I had to fix various "Num doesn't imply EQ" issues as well as a lot of general typesystem issues. Imagine annual changes to the C programming language that require not only recompiliton but rewrites! So let's get rid of this crap. Ciao, Kili
Re: Icinga Port in 5.3 - missing "-m" for /var/icinga
On 2013/05/07 12:37, Sebastian Rother wrote: > Dear Stuart, dear Ports@-List; > > I wanted to test icinga on OpenBSD 5.3 and noticed the following: > > # pkg_add icinga > icinga-1.8.4:nagios-plugins-1.4.16: ok > icinga-1.8.4:libltdl-2.4.2: ok > useradd: Warning: home directory `/var/icinga' doesn't exist, and -m was > not specified > icinga-1.8.4: ok > > Is that a glitch in the Port or realy desired? > The directory seams to get created later and it exists just the error is > annoying. > > # ls > /var/icinga/ > archives rw > # > > > Kind regards, > Sebastian > > p.s. > Thank you very much for the Port Stuart. This happens with various ports, annoying but it can be ignored.
seamonkey-i18n-* activation instructions [Was: Re: thunderbird-i18n, firefox-i18n: pkg/MESSAGE: new lang activation advice]
lan...@rhaalovely.net (Landry Breuil), 2013.05.06 (Mon) 16:55 (CEST): > On Fri, May 03, 2013 at 11:00:11AM +0200, MERIGHI Marcus wrote: > > since the old advice did not work for me and I finally found out what to > > do there's a patch: > I'll include this in the next fx/tb update - can you check seamonkey too > ? Thx! (putting ports@ back in, I hope you do not mind if I post these lines of you publicly...) I do not usually use seamonkey but did real-world testing. Patches inlined below and attached as well for ease of use. With seamonkey things are a bit different: an installed language pack appears as a language add-on and needs to be activated. Activation is supposed to be asked for automagically after restart of Seamonkey. If not it needs to be done manually. After that the language is not yet used, needs to be selected the old way additionally. for seamonkey I rephrased README-main: Index: README-main === RCS file: /cvs/ports/www/seamonkey/pkg/README-main,v retrieving revision 1.4 diff -u -r1.4 README-main --- README-main 10 Oct 2012 21:03:40 - 1.4 +++ README-main 7 May 2013 09:53:11 - @@ -15,10 +15,14 @@ Internationalization -This package contains internationalizations for all supported -languages. To configure Seamonkey for your language, go to -Edit->Preferences->Appearance->Languages/Content and select your -favorite Language/Content pack. +There are packages containing internationalizations for all supported +languages. To use Seamonkey in your language, install one of the +seamonkey-i18n-* packages and start Seamonkey. If you are not asked for +confirmation of activation of the language pack, go to +Tools->Add-ons manager->Languages and click 'activate' on your language +pack. Then go to +Edit->Preferences->Appearance and select your favorite Language/Content +in the 'User Interface Language' pull down menu. Restart Seamonkey. Debugging = for seamonkey-i18n I added MESSAGE to seamonkey-i18n/pkg: --- /dev/null Tue May 7 12:00:51 2013 +++ MESSAGE Tue May 7 11:59:10 2013 @@ -0,0 +1,5 @@ +To configure Seamonkey for your language, start Seamonkey. +If you are not asked for confirmation of activation of the language pack, +go to Tools->Add-ons manager->Languages and click 'activate' on your +language pack. Then go to Edit->Preferences->Appearance and select your +favorite Language/Content in the 'User Interface Language' pull down menu. > !DSPAM:5187c88216817880116685! Index: README-main === RCS file: /cvs/ports/www/seamonkey/pkg/README-main,v retrieving revision 1.4 diff -u -r1.4 README-main --- README-main 10 Oct 2012 21:03:40 - 1.4 +++ README-main 7 May 2013 09:53:11 - @@ -15,10 +15,14 @@ Internationalization -This package contains internationalizations for all supported -languages. To configure Seamonkey for your language, go to -Edit->Preferences->Appearance->Languages/Content and select your -favorite Language/Content pack. +There are packages containing internationalizations for all supported +languages. To use Seamonkey in your language, install one of the +seamonkey-i18n-* packages and start Seamonkey. If you are not asked for +confirmation of activation of the language pack, go to +Tools->Add-ons manager->Languages and click 'activate' on your language +pack. Then go to +Edit->Preferences->Appearance and select your favorite Language/Content +in the 'User Interface Language' pull down menu. Restart Seamonkey. Debugging = --- /dev/null Tue May 7 12:00:51 2013 +++ MESSAGE Tue May 7 11:59:10 2013 @@ -0,0 +1,5 @@ +To configure Seamonkey for your language, start Seamonkey. +If you are not asked for confirmation of activation of the language pack, +go to Tools->Add-ons manager->Languages and click 'activate' on your +language pack. Then go to Edit->Preferences->Appearance and select your +favorite Language/Content in the 'User Interface Language' pull down menu.
