Re: Bluetooth OBEX to my phone

2009-01-12 Thread Vadim Zhukov
On 13 January 2009 г. 03:42:48 andrew fresh wrote:
> On Fri, Jan 09, 2009 at 10:18:41PM +, Stuart Henderson wrote:
> > Not sure if this will help, but with the Broadcom BT-253 in the
> > Eee 901, I can do this:
> >
> > sudo btconfig ubt0 up
> > sudo btconfig ubt0 name "some name"
> > sudo bthcid
> > btconfig ubt0 inq
> > vi /etc/bluetooth/hosts
> >   add address for remote device here e.g. nokia1
> > sudo btpin -r -a nokia1
> >   this generates a temporary PIN to type into the phone to pair
> >   with the computer; alternatively you can use a preset PIN with
> >   -p instead of -r
> > rfcomm_sppd -a nokia1 -s DUN
> >   if not already paired, the phone will ask for the PIN from above
> >   to allow pairing.
> >   AT modem commands work, ^C to exit, or you can get it to attach
> >   to a pty where you can run PPP
> > sdpquery -a nokia1 Browse
> >   big long list
> >
> > but what I can't do is this:
> >
> > obexftp -b nokia1 -X -vvv
> >   error on connect(): Undefined error: 0
>
> I get these same results on my laptop:
> OpenBSD 4.4-current (GENERIC) #1650: Sat Jan 10 12:32:20 MST 2009
> t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>
> With the built-in bluetooth:
> ubt0 at uhub3 port 1 "ALPS UGX" rev 2.00/19.15 addr 2
>
> but, if I try this one, it still doesn't work.
> ubt1 at uhub1 port 1 "Cambridge Silicon Radio Bluetooth" rev 1.10/5.25
> addr 2
>
>
> so, I guess it is that the bluetooth adapters I have that aren't
> supported, and obexftp doesn't really work over the bluetooth I have.

Very likely to be. I have two BlueTooth sticks, both says they are:

ubt0 at uhub1 port 2 "Cambridge Silicon Radio Bluetooth" rev 2.00/31.64 
addr 2
bthub0 at ubt0 00:15:83:04:1a:a8
ubt1 at uhub1 port 1 "Cambridge Silicon Radio Bluetooth" rev 2.00/31.64 
addr 3
bthub1 at ubt1 00:18:e4:0a:b3:19

But only one is working fine with my mobile phone (Siemens CX75);
another one just allows to discover phone, but rfcomm_sppd(1)
(offtopic: should not it be section 8?) fails to connect.

-- 
  Best wishes,
Vadim Zhukov



Re: UPDATE: mcs and mowgli

2009-01-12 Thread Federico G. Schwindt
> [..]
> 
> > You'll see that the environment can't override it. And you'll see
> > that there's a bug in the buildsys if the flags from the Makefile
> > are not used. And that'd be something for me to fix then, and
> > that'd be a case to disable .SILENT.
> 
> If I've to review a port with a too quiet Makefile and if it takes
> more just five minutes to make it less quiet, I usually just remove
> the port submission from my inbox without any further comment.

  I appreciate everyone's output, but can we concentrate on the ports?
  I think most of us agree about the silent vs. verbose Makefile, so let's
move forward.

  f.-



UPDATE: imapproxy 1.2.7

2009-01-12 Thread Brad
The imapproxy 1.2.7 release is coming up soon. Please test.
I never received any feedback about 1.2.6.


Index: Makefile
===
RCS file: /cvs/ports/mail/imapproxy/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- Makefile12 Sep 2007 19:54:48 -  1.6
+++ Makefile13 Jan 2009 03:51:58 -
@@ -2,38 +2,35 @@
 
 COMMENT=   caching IMAP proxy to be used with webmail clients
 
-DISTNAME=  up-imapproxy-1.2.5
-PKGNAME=   ${DISTNAME:S/^up-//}p1
+DISTNAME=  up-imapproxy-1.2.7rc2
+PKGNAME=   ${DISTNAME:S/^up-//}
 CATEGORIES=mail
+MASTER_SITES=  ${HOMEPAGE}/downloads/
 
 HOMEPAGE=  http://www.imapproxy.org/
 
 MAINTAINER=Holger Mauermann 
 
-# GPL
+# GPLv2+
 PERMIT_PACKAGE_CDROM=  Yes
 PERMIT_PACKAGE_FTP=Yes
 PERMIT_DISTFILES_CDROM=Yes
 PERMIT_DISTFILES_FTP=  Yes
+WANTLIB=   curses c ssl.>=12.0 crypto pthread
 
-MASTER_SITES=  ${HOMEPAGE}/downloads/
-
-WANTLIB=   curses c ssl crypto pthread
-
-CONFIGURE_STYLE=gnu
+CONFIGURE_STYLE= gnu
 
 NO_REGRESS=Yes
 
 pre-build:
-   @perl -pi -e "s,!!SYSCONFDIR!!,${SYSCONFDIR}," \
-   ${WRKSRC}/include/imapproxy.h
+   @${SUBST_CMD} ${WRKSRC}/include/imapproxy.h
 
 post-install:
-   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/imapproxy
-   ${INSTALL_DATA} ${WRKSRC}/scripts/imapproxy.conf \
-   ${PREFIX}/share/examples/imapproxy
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/imapproxy
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/imapproxy
${INSTALL_DATA} ${WRKSRC}/README ${WRKSRC}/README.ssl \
${PREFIX}/share/doc/imapproxy
+   ${INSTALL_DATA} ${WRKSRC}/scripts/imapproxy.conf \
+   ${PREFIX}/share/examples/imapproxy
 
 .include 
Index: distinfo
===
RCS file: /cvs/ports/mail/imapproxy/distinfo,v
retrieving revision 1.3
diff -u -p -r1.3 distinfo
--- distinfo11 Apr 2007 16:06:46 -  1.3
+++ distinfo13 Jan 2009 03:48:34 -
@@ -1,5 +1,5 @@
-MD5 (up-imapproxy-1.2.5.tar.gz) = xt+wn9vYwK+GLdAgSa456Q==
-RMD160 (up-imapproxy-1.2.5.tar.gz) = OuYsroFrdg4fdoZ4xYifbsN5iec=
-SHA1 (up-imapproxy-1.2.5.tar.gz) = B4UfBXw1HgQho1HJSUw8uXETAo4=
-SHA256 (up-imapproxy-1.2.5.tar.gz) = 
eJQKF25G+YZjgds4+phzuve3dNzlvEIulRmYkpaGkfg=
-SIZE (up-imapproxy-1.2.5.tar.gz) = 132317
+MD5 (up-imapproxy-1.2.7rc2.tar.gz) = hr64yi3C+DD4KBAy1qBb3w==
+RMD160 (up-imapproxy-1.2.7rc2.tar.gz) = MmkynwINiUy0kphtNkWMBGDqqw8=
+SHA1 (up-imapproxy-1.2.7rc2.tar.gz) = sm+YI7Tnrrp0zmBTjE1RepIFXBg=
+SHA256 (up-imapproxy-1.2.7rc2.tar.gz) = 
4vXhYx8zeilAqFaQRnoITeQgXAKehCfZruSoUhuXFpo=
+SIZE (up-imapproxy-1.2.7rc2.tar.gz) = 136832
Index: patches/patch-Makefile_in
===
RCS file: /cvs/ports/mail/imapproxy/patches/patch-Makefile_in,v
retrieving revision 1.2
diff -u -p -r1.2 patch-Makefile_in
--- patches/patch-Makefile_in   12 Sep 2007 19:54:48 -  1.2
+++ patches/patch-Makefile_in   14 Mar 2008 01:57:54 -
@@ -1,6 +1,6 @@
 Makefile.in.orig   Tue Jan 30 10:23:46 2007
-+++ Makefile.inWed Aug 22 02:53:26 2007
-@@ -53,7 +53,7 @@ TAT_OBJ = ./src/pimpstat.o ./src/config.o
+--- Makefile.in.orig   Mon Jan 28 08:15:08 2008
 Makefile.inThu Mar 13 21:57:46 2008
+@@ -54,7 +54,7 @@ TAT_OBJ = ./src/pimpstat.o ./src/config.o
  
  # Final targets
  
@@ -9,7 +9,7 @@
  TAT_BIN = ./bin/pimpstat
  
  # Rules
-@@ -78,9 +78,9 @@ distclean: clean
+@@ -79,9 +79,9 @@ distclean: clean
rm -f config.cache config.log config.h Makefile
  
  install: $(XYD_BIN) $(TAT_BIN)
Index: patches/patch-imapcommon_c
===
RCS file: patches/patch-imapcommon_c
diff -N patches/patch-imapcommon_c
--- patches/patch-imapcommon_c  11 Apr 2007 16:06:46 -  1.2
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,10 +0,0 @@
 src/imapcommon.c.orig  Tue Oct  3 14:27:00 2006
-+++ src/imapcommon.c   Wed Jan 24 22:35:30 2007
-@@ -138,6 +138,7 @@
- #include 
- 
- #include 
-+#include 
- #include 
- 
- #include 
Index: patches/patch-imapproxy_h
===
RCS file: /cvs/ports/mail/imapproxy/patches/patch-imapproxy_h,v
retrieving revision 1.3
diff -u -p -r1.3 patch-imapproxy_h
--- patches/patch-imapproxy_h   12 Sep 2007 19:54:48 -  1.3
+++ patches/patch-imapproxy_h   30 Dec 2008 07:58:14 -
@@ -1,6 +1,6 @@
 include/imapproxy.h.orig   Tue Jan 30 10:23:46 2007
-+++ include/imapproxy.hWed Aug 22 02:53:26 2007
-@@ -151,7 +151,7 @@
+--- include/imapproxy.h.orig   Mon Oct 20 09:51:51 2008
 include/imapproxy.hTue Dec 30 02:58:08 2008
+@@ -163,7 +163,7 @@
  /* 
   * Common definitions 
   */
@@ -9,12 +9,12 @@
  #define IMAP_UNTAGGED_OK"* OK "   /* untagged OK response
*/
  #define IMAP_TAGGED_OK  "1 OK 

UPDATE: Pidgin 2.5.4

2009-01-12 Thread Brad
Here is an update to Pidgin 2.5.4. Please test.


Index: Makefile
===
RCS file: /cvs/ports/net/pidgin/Makefile,v
retrieving revision 1.33
diff -u -p -r1.33 Makefile
--- Makefile27 Dec 2008 20:48:00 -  1.33
+++ Makefile13 Jan 2009 03:14:59 -
@@ -4,14 +4,15 @@ SHARED_ONLY=  Yes
 
 COMMENT=   multi-protocol instant messaging client
 
-DISTNAME=  pidgin-2.5.3
+DISTNAME=  pidgin-2.5.4
 CATEGORIES=net
+MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=pidgin/}
 
 SHARED_LIBS+=  jabber  0.0
 SHARED_LIBS+=  oscar   0.0
-SHARED_LIBS+=  purple  4.3
-SHARED_LIBS+=  purple-client   4.3
-SHARED_LIBS+=  gnt 4.3
+SHARED_LIBS+=  purple  4.4
+SHARED_LIBS+=  purple-client   4.4
+SHARED_LIBS+=  gnt 4.4
 
 HOMEPAGE=  http://pidgin.im/
 
@@ -29,8 +30,6 @@ WANTLIB=  ICE SM X11 Xau Xcomposite Xcur
gthread-2.0 m ncurses panel pango-1.0 pangocairo-1.0 \
pangoft2-1.0 pcre pixman-1 png pthread ssl stdc++ z
 
-MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=pidgin/}
-
 MODULES=   devel/gettext textproc/intltool
 
 BUILD_DEPENDS= :gconf2-*:devel/gconf2 \
@@ -60,6 +59,7 @@ CONFIGURE_STYLE= autoconf
 AUTOCONF_VERSION= 2.61
 CONFIGURE_ARGS+= 
--with-gconf-schema-file-dir=${LOCALBASE}/share/schemas/pidgin \
 --disable-avahi \
+--disable-doxygen \
 --disable-gevolution \
 --disable-gnutls \
 --disable-nm \
Index: distinfo
===
RCS file: /cvs/ports/net/pidgin/distinfo,v
retrieving revision 1.16
diff -u -p -r1.16 distinfo
--- distinfo27 Dec 2008 20:48:00 -  1.16
+++ distinfo13 Jan 2009 03:03:22 -
@@ -1,5 +1,5 @@
-MD5 (pidgin-2.5.3.tar.gz) = R8bs1Fs6YseoJvfOsmY/uA==
-RMD160 (pidgin-2.5.3.tar.gz) = 6Pa8eC+ve6Ca+z//QCpbm7uHEIM=
-SHA1 (pidgin-2.5.3.tar.gz) = Nt3RfMXMCwJPJF11shLfv51cKRQ=
-SHA256 (pidgin-2.5.3.tar.gz) = 1q8MqS5Gzj5l1+lWc9heI1OrkWzTLoqglioGgZtwMxQ=
-SIZE (pidgin-2.5.3.tar.gz) = 11874548
+MD5 (pidgin-2.5.4.tar.gz) = 6yjFUmR+5YPz2BfbaQFkxQ==
+RMD160 (pidgin-2.5.4.tar.gz) = S6ZxYbhQzrsBvLosFtKGc+2XEUg=
+SHA1 (pidgin-2.5.4.tar.gz) = wOw4oNIMLYYVtBNuWVUFYfpQcEg=
+SHA256 (pidgin-2.5.4.tar.gz) = Z0kcNGSDMBzFYO9Z9XJ9Gxgp2LYJzl1XwpVv8Lij0Vg=
+SIZE (pidgin-2.5.4.tar.gz) = 11876135
Index: patches/patch-finch_libgnt_gntmain_c
===
RCS file: patches/patch-finch_libgnt_gntmain_c
diff -N patches/patch-finch_libgnt_gntmain_c
--- patches/patch-finch_libgnt_gntmain_c9 Dec 2007 10:56:31 -   
1.4
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,12 +0,0 @@
-$OpenBSD: patch-finch_libgnt_gntmain_c,v 1.4 2007/12/09 10:56:31 steven Exp $
 finch/libgnt/gntmain.c.origFri Dec  7 15:37:00 2007
-+++ finch/libgnt/gntmain.c Sat Dec  8 21:04:07 2007
-@@ -21,7 +21,7 @@
-  */
- 
- #define _GNU_SOURCE
--#if (defined(__APPLE__) || defined(__unix__)) && !defined(__FreeBSD__)
-+#if (defined(__APPLE__) || defined(__unix__)) && !defined(__FreeBSD__) && 
!defined(__OpenBSD__)
- #define _XOPEN_SOURCE_EXTENDED
- #endif
- 
Index: patches/patch-finch_libgnt_gntwm_c
===
RCS file: patches/patch-finch_libgnt_gntwm_c
diff -N patches/patch-finch_libgnt_gntwm_c
--- patches/patch-finch_libgnt_gntwm_c  24 Mar 2008 08:23:22 -  1.5
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,12 +0,0 @@
-$OpenBSD: patch-finch_libgnt_gntwm_c,v 1.5 2008/03/24 08:23:22 steven Exp $
 finch/libgnt/gntwm.c.orig  Fri Feb 29 13:09:19 2008
-+++ finch/libgnt/gntwm.c   Sat Mar 22 10:28:39 2008
-@@ -26,7 +26,7 @@
- #include 
- #else
- #define _GNU_SOURCE
--#if (defined(__APPLE__) || defined(__unix__)) && !defined(__FreeBSD__)
-+#if (defined(__APPLE__) || defined(__unix__)) && !defined(__FreeBSD__) && 
!defined(__OpenBSD__)
- #define _XOPEN_SOURCE_EXTENDED
- #endif
- #endif
Index: patches/patch-libpurple_nat-pmp_c
===
RCS file: patches/patch-libpurple_nat-pmp_c
diff -N patches/patch-libpurple_nat-pmp_c
--- patches/patch-libpurple_nat-pmp_c   21 Aug 2008 05:59:01 -  1.4
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,12 +0,0 @@
-$OpenBSD: patch-libpurple_nat-pmp_c,v 1.4 2008/08/21 05:59:01 brad Exp $
 libpurple/nat-pmp.c.orig   Mon Aug 18 21:53:31 2008
-+++ libpurple/nat-pmp.cWed Aug 20 00:48:35 2008
-@@ -47,6 +47,8 @@
- #include 
- #endif
- 
-+#undef NET_RT_DUMP
-+
- /* We will need sysctl() and NET_RT_DUMP, both of which are not present
-  * on all platforms, to continue. */
- #if defined(HAVE_SYS_SYSCTL_H) && defined(NET_RT_DUMP)
Index: patches/patch-pidgin_gtkdialogs_c
===
RCS file: /cvs/ports/net/pidgin/patches/patch-pidgin_gtk

Re: Bluetooth OBEX to my phone

2009-01-12 Thread andrew fresh
On Fri, Jan 09, 2009 at 10:18:41PM +, Stuart Henderson wrote:
> Not sure if this will help, but with the Broadcom BT-253 in the
> Eee 901, I can do this:
> 
> sudo btconfig ubt0 up
> sudo btconfig ubt0 name "some name"
> sudo bthcid
> btconfig ubt0 inq
> vi /etc/bluetooth/hosts
>   add address for remote device here e.g. nokia1
> sudo btpin -r -a nokia1
>   this generates a temporary PIN to type into the phone to pair
>   with the computer; alternatively you can use a preset PIN with
>   -p instead of -r
> rfcomm_sppd -a nokia1 -s DUN
>   if not already paired, the phone will ask for the PIN from above
>   to allow pairing.
>   AT modem commands work, ^C to exit, or you can get it to attach
>   to a pty where you can run PPP
> sdpquery -a nokia1 Browse
>   big long list
> 
> but what I can't do is this:
> 
> obexftp -b nokia1 -X -vvv
>   error on connect(): Undefined error: 0
> 

I get these same results on my laptop:
OpenBSD 4.4-current (GENERIC) #1650: Sat Jan 10 12:32:20 MST 2009
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

With the built-in bluetooth:
ubt0 at uhub3 port 1 "ALPS UGX" rev 2.00/19.15 addr 2

but, if I try this one, it still doesn't work.
ubt1 at uhub1 port 1 "Cambridge Silicon Radio Bluetooth" rev 1.10/5.25 addr 2


so, I guess it is that the bluetooth adapters I have that aren't
supported, and obexftp doesn't really work over the bluetooth I have.


l8rZ,
-- 
andrew - ICQ# 253198 - Jabber: and...@rraz.net

BOFH excuse of the day: Out of cards on drive D:



PATCH: lang/gcc/4.2 (list)

2009-01-12 Thread Mikolaj Kucharski
[resending to the list after maintainer timeout]

Currently gcc-4.2.20070307p8 is required by libstdc++-4.2.20070307p4. Is
it really the case? Please review attached diff. Thanks.

-- 
best regards
q#
Index: Makefile
===
RCS file: /cvs/ports/lang/gcc/4.2/Makefile,v
retrieving revision 1.23
diff -u -r1.23 Makefile
--- Makefile11 Sep 2008 19:22:05 -  1.23
+++ Makefile8 Jan 2009 00:56:58 -
@@ -10,7 +10,7 @@
 
 PKGNAME-main=  gcc-${FULL_PKGVERSION}p8
 PKGNAME-c++ =  g++-${FULL_PKGVERSION}p7
-PKGNAME-estdc= libstdc++-${FULL_PKGVERSION}p4
+PKGNAME-estdc= libstdc++-${FULL_PKGVERSION}p5
 PKGNAME-g77=   g77-${FULL_PKGVERSION}p4
 PKGNAME-f95=   g95-${FULL_PKGVERSION}p7
 PKGNAME-java=  gcj-${FULL_PKGVERSION}p3
@@ -184,6 +184,7 @@
 WANTLIB=   c
 
 RUN_DEPENDS-main=
+RUN_DEPENDS-estdc=
 
 RUN_DEPENDS-c++ =  ${RUN_DEPENDS} ::${PKGPATH},-estdc
 WANTLIB-estdc= c m


Re: UPDATE: Xine-lib 1.1.16

2009-01-12 Thread Dawe

Brad wrote:

On Sat, Jan 10, 2009 at 06:26:52PM -0500, Brad wrote:

On Thu, Jan 08, 2009 at 02:21:37AM -0500, Brad wrote:

Here is an update to Xine-lib 1.1.16. A bunch of security fixes
and a lot of bug fixes.

* Security fixes:
  - Heap overflow in Quicktime atom parsing.  (CVE-2008-5234 vector 1)
  - Multiple buffer overflows.(CVE-2008-5236)
  - Multiple integer overflows.   (CVE-2008-5237)
  - Unchecked read function results.  (CVE-2008-5239)
  - Unchecked malloc using untrusted values.  (CVE-2008-5240 vectors 3 & 4)
  - Buffer indexing using an untrusted value. (CVE-2008-5243)

Please test.

If you had problems building the previous revision of this diff please
try this revision as it should resolve those issues..


A quick 1.1.16.1 release has been made which consits of mainly
bug fixes, build fixes and a regression fix or two for 1.1.16.
Please test.


Works for me on amd64 but not so much on i386.
There xine can't play ogg audio any more, though the xineplug_dmx_ogg.so
is there. With mp4 it's only able to play video, no sound. It complains 
about missing demuxer plugins in both cases.

I'm pretty sure it worked with the 1.1.16 patch on i386, too.
Other stuff like mp3 is still ok.



Re: UPDATE: mcs and mowgli

2009-01-12 Thread Matthias Kilian
On Mon, Jan 12, 2009 at 09:55:32PM +0100, Jonathan Schleifer wrote:
> >No, it isn't. There may be errors in the Makefile. There may be
> >overrides in the environment and/or command line that may *not*
> >work as desired which you can't check by just looking at the Makefile.
> 
> Have you actually looked at the Makefile and buildsys.mk.in?

To be honest: no, because I'm not involved in mowgli (nor in mcs).
And I didn't want to argue about this specific software (nor to
blame it our you) -- I'm arguing about too silent Makefiles in
general.

>From my point of view (as a porter), Makefiles hiding details, or
Makefiles I have to look at before I can be sure that they don't
lie, are just additional work. And hiding details doesn't give
anyone anything IMHO.

During the last two weeks, I've seen at least one project with a
Makefile hiding details and producing fancy output and actually
*not* applying CFLAGS correctly in all targets. Unfortunately, I
don't remember which project it was (none of yours, maybe something
from suckless.org).

And there are even worse examples, like this Cabal thingy used in
the Haskell world.

> You'll see that the environment can't override it. And you'll see
> that there's a bug in the buildsys if the flags from the Makefile
> are not used. And that'd be something for me to fix then, and
> that'd be a case to disable .SILENT.

If I've to review a port with a too quiet Makefile and if it takes
more just five minutes to make it less quiet, I usually just remove
the port submission from my inbox without any further comment.

Ciao,
Kili



Re: UPDATE: mcs and mowgli

2009-01-12 Thread Jonathan Schleifer

Am 12.01.2009 um 21:48 schrieb Matthias Kilian:


No, it isn't. There may be errors in the Makefile. There may be
overrides in the environment and/or command line that may *not*
work as desired which you can't check by just looking at the Makefile.


Have you actually looked at the Makefile and buildsys.mk.in? You'll  
see that the environment can't override it. And you'll see that  
there's a bug in the buildsys if the flags from the Makefile are not  
used. And that'd be something for me to fix then, and that'd be a case  
to disable .SILENT.



And there are people like me who want to check wether a Makefile
correctly picks up CFLAGS, CC etc. if overridden. Like (in a port's
directory): DEBUG=-g make


Just look at buildsys.mk. All flags you had in your env when running  
configure are written there.


--
Jonathan



PGP.sig
Description: Signierter Teil der Nachricht


Re: UPDATE: mcs and mowgli

2009-01-12 Thread Matthias Kilian
On Mon, Jan 12, 2009 at 04:20:41PM +0100, Jonathan Schleifer wrote:
> >I don't know others, but as developer I would never prefer colorful
> >output over the real one, and I don't find it very useful, neither  
> >for me
> >nor for anyone who might need to report issues during building.
> 
> Well, you see the compiler and linker flags if you look at the  
> Makefile. This is usually enough.

No, it isn't. There may be errors in the Makefile. There may be
overrides in the environment and/or command line that may *not*
work as desired which you can't check by just looking at the Makefile.

And there are people like me who want to check wether a Makefile
correctly picks up CFLAGS, CC etc. if overridden. Like (in a port's
directory): DEBUG=-g make

Ciao,
Ki "Makefile nazi" li

-- 
C programmers never die. They're just cast into void.



graphics/evince weirdness

2009-01-12 Thread Alexey Suslikov
$ sudo pkg_add packages/evince-2.24.2p1.tgz
ghostscript-8.63p2: complete
Can't install ghostscript-8.63p2-gtk because of conflicts (ghostscript-8.63p2)
/usr/sbin/pkg_add: ghostscript-8.63p2-gtk:Fatal error

$ pkg_info
ORBit2-2.14.16  high-performance CORBA Object Request Broker
OpenEXR-1.6.1p0 high dynamic range image format
aalib-1.4   ascii art library
alacarte-0.11.6p2   easy GNOME menu editing tool
arts-1.5.10 K Desktop Environment, aRTs
aspell-0.60.6p3 spell checker designed to eventually replace Ispell
atk-1.24.0  accessibility toolkit used by gtk+
audacity-1.3.4p3free audio editor
autoconf-2.13p1 automatically configure source code on many Un*x platforms
autoconf-2.52p3 automatically configure source code on many Un*x platforms
autoconf-2.59p3 automatically configure source code on many Un*x platforms
autoconf-2.61p3 automatically configure source code on many Un*x platforms
autoconf-2.62   automatically configure source code on many Un*x platforms
automake-1.4.6  GNU Standards-compliant Makefile generator
automake-1.9.6p2GNU standards-compliant Makefile generator
babl-0.0.22 dynamic pixel format conversion library
bash-3.2.48 GNU Bourne Again Shell
bison-2.3   GNU parser generator
bug-buddy-2.24.2p0  graphical bug reporting tool for GNOME
bzip2-1.0.5 block-sorting file compressor, unencumbered
c-client-2007b  University of Washington's c-client mail access routines
cabextract-1.2p0extracts files from Microsoft CAB archives
cairo-1.8.4 vector graphics library
cdparanoia-3.a9.8p0 CDDA reading utility with extra data verification features
control-center2-2.24.0.1p2 GNOME control center
cppunit-1.12.1  c++ unit testing framework
cups-1.2.7p14   Common Unix Printing System
curl-7.19.2 get files from FTP, Gopher, HTTP or HTTPS servers
cyrus-sasl-2.1.22p4 RFC  SASL (Simple Authentication and Security Layer)
db-4.6.21   Berkeley DB package, revision 4
dbus-1.2.6  message bus system
dbus-glib-0.78  glib bindings for dbus message system
dbus-python-0.83.0p0 dbus bindings for Python
desktop-file-utils-0.15 utilities for 'desktop' entries
detex-2.8   strip TeX/LaTeX codes from a file
devhelp-0.22p0  API documentation browser for GNOME
djvulibre-3.5.21view, decode and encode DjVu files
docbook-4.4 technical documentation XML/SGML definitions
docbook-dsssl-1.72  modular DSSSL stylesheets for the DocBook DTD
docbook-xsl-1.68.1p1 docbook XSL modular stylesheet
dvi2tty-5.3.1   converts .dvi files to plain text
eel-2.24.1  Eazel Extensions Library
ekiga-2.0.12p6  SIP and H.323 compatible conferencing application
enchant-1.4.2p0 generic spell checking library/wrapper
eog-2.24.2p0Eye of GNOME, image viewing and cataloging program
esound-0.2.41v0 sound library for Enlightenment
evolution-data-server-2.24.2 data backends for the Evolution mail/PIM suite
faac-1.26   MPEG-2 and MPEG-4 AAC encoder
faad-2.6.1  MPEG-2 and MPEG-4 AAC decoder
fam-2.7.0p6 File Alteration Monitor
ffmpeg-20080620p5   audio/video converter and streamer with bktr(4) support
file-roller-2.24.2p1 archive manager for GNOME
flac-1.2.1p0free lossless audio codec
fping-2.4b2p4   quickly ping N hosts w/o flooding the network
freetds-0.63p1  project to document and implement the TDS protocol
fribidi-0.10.4p0library implementing the Unicode Bidirectional Algorithm
g++-4.2.20070307p7  GNU compiler collection: C++ compiler
gcalctool-5.24.2p0  GTK2 desktop calculator
gcc-4.2.20070307p8  GNU compiler collection: core C compiler
gconf2-2.24.0   configuration database system for GNOME
gcpio-2.9   GNU copy-in/out (cpio)
gdbm-1.8.3p0GNU dbm
gdm-2.20.8p7GNOME display manager
gedit-2.24.2p0  lightweight GNOME text editor
gegl-0.0.22 graph based image processing framework
gettext-0.17p0  GNU gettext
gftp-2.0.19 multithreaded gtk2 file transfer client
ghostscript-8.63p2  GNU PostScript interpreter
ghostscript-fonts-8.11p0 35 standard PostScript fonts with Adobe name aliases
gimp-2.6.3  GNU Image Manipulation Program
glib-1.2.10p3   useful routines for C programming
glib2-2.18.3p0  general-purpose utility library
glib2-fam-2.18.3fam(3) gio module
glitz-0.5.6p0   OpenGL image compositing library
gmake-3.81p0GNU make
gmp-4.2.4   library for arbitrary precision arithmetic
gnome-applets2-2.24.2p2 applets for use with the GNOME panel
gnome-audio-2.22.2  audio files for Gnome
gnome-backgrounds-2.24.0 wallpapers for GNOME
gnome-desktop-2.24.2p0 components for the GNOME desktop
gnome-doc-utils-0.10.3p7 collection of documentation utilities for the
GNOME project
gnome-icon-theme-2.24.0 base icon theme for GNOME
gnome-keyring-2.24.1 password agent for the GNOME project
gnome-media-2.24.0.1p0 GNOME media utilities
gnome-menus-2.24.2  imple

Re: UPDATE: mcs and mowgli

2009-01-12 Thread Stuart Henderson
On 2009/01/12 18:54, Jonathan Schleifer wrote:
>> imho it is a bit ugly, but if being able to see the compiler command
>> lines requires slightly ugly output, I'd rather have the ugly output.
>> (i'd prefer it even more with a proper option that hides the internal
>> build system logic and the lines like "CC foo.c" and just prints the
>> command invocations..)
>
> I could maybe add a mode that still uses .SILENT, but instead out  
> outputting coloured text could output the command line executed. Like  
> replace the yellow printf by outputting the command line and remove  
> the green and red output.

I think that would be useful.

>> if people are tracking down a build problem, or if they're grepping
>> logs from a bulk build looking for something, or even the simple case
>> of making sure CC/CFLAGS are honoured, full command lines are often
>> invaluable.
>
> Usually, attaching the definitions of buildsys.mk is enough for that.  
> If they aren't honoured, it's a bug in the buildsys and something I  
> have to track down, not the user :).  Removing .SILENT is really only  
> to track down bugs in the buildsys itself. Anyway, do you also patch  
> all those ports using other buildsyses that don't output the command  
> line? If so, you got a lot of work ;)

We have to take a wider view, since there are hundreds of build
systems in the ports tree, and I'm sure you won't be too surprised
at what people make autoconf do... :) We usually do check command
lines for things like CFLAGS being honoured, so yes, we often do
patch them. (This isn't just for the sake of it; for example; the
compiler on some of the arch we build packages on doesn't work
too well with certain -O values, so we have to force them).

> PS: There's no need to always CC me, I'm on the list. And so are you.  
> That's why I always only send to ports@openbsd.org :)

I'll try and remember. If your MUA lets you set Mail-Followup-To
I think you'll find most people here honour it. Group-reply is the
normal way on OpenBSD lists.



Re: UPDATE: mcs and mowgli

2009-01-12 Thread Jonathan Schleifer

Am 12.01.2009 um 18:23 schrieb Stuart Henderson:


imho it is a bit ugly, but if being able to see the compiler command
lines requires slightly ugly output, I'd rather have the ugly output.
(i'd prefer it even more with a proper option that hides the internal
build system logic and the lines like "CC foo.c" and just prints the
command invocations..)


I could maybe add a mode that still uses .SILENT, but instead out  
outputting coloured text could output the command line executed. Like  
replace the yellow printf by outputting the command line and remove  
the green and red output.



if people are tracking down a build problem, or if they're grepping
logs from a bulk build looking for something, or even the simple case
of making sure CC/CFLAGS are honoured, full command lines are often
invaluable.


Usually, attaching the definitions of buildsys.mk is enough for that.  
If they aren't honoured, it's a bug in the buildsys and something I  
have to track down, not the user :). Removing .SILENT is really only  
to track down bugs in the buildsys itself. Anyway, do you also patch  
all those ports using other buildsyses that don't output the command  
line? If so, you got a lot of work ;)


PS: There's no need to always CC me, I'm on the list. And so are you.  
That's why I always only send to ports@openbsd.org :)


--
Jonathan



PGP.sig
Description: Signierter Teil der Nachricht


NEW: math/wcalc

2009-01-12 Thread Amarendra Godbole
Hello,

My first port, and I think I have followed all the porting guidelines.

http://www.obscure.org/~amunix/tmp/wcalc.tar.gz (and also attached)

pkg/DESCR:
wcalc is a powerful arbitrary-precision calculator. It has standard
functions (sin, asinh, logtwo, floor, etc), many pre-defined constants
(pi, e, c, etc.), variables, "active" variables, command history, and
hex/octal/binary i/o, conversions, and more.

Though there exists a math/calc, I decided to port this to gain
experience porting to OpenBSD. I maintain this port on FreeBSD, and
hence it was a natural choice. As indicated in the porting guidelines,
I did an audit of the source, and indicated a few issues upstream. The
patches are a result of this, and they have been committed upstream
already.

Tested only on an i386, since I don't have any other box. I'd
appreciate feedback, and improvements that can be made, so that I can
be better next time on. Thanks in advance.

-Amarendra


wcalc.tar.gz
Description: GNU Zip compressed data


Re: UPDATE: mcs and mowgli

2009-01-12 Thread Stuart Henderson
On 2009/01/12 16:20, Jonathan Schleifer wrote:
> Am 12.01.2009 um 16:14 schrieb Federico G. Schwindt:
>
>> I don't know others, but as developer I would never prefer colorful
>> output over the real one, and I don't find it very useful, neither  
>> for me
>> nor for anyone who might need to report issues during building.
>
> Well, you see the compiler and linker flags if you look at the  
> Makefile. This is usually enough. If those aren't adeded on build for  
> some reason, that's a bug in the buildsys - and then you'd need to  
> disable .SILENT: :) Normal users should never need to do that, and  
> even developers, if they aren't buildsys developers, usually never  
> need to do that.
>
>> I think as it is with the diff is fine, it's simple and does the job.
>
> I consider that very ugly. You have useless printfs there and also the 
> the printfs in the output. So you actually see a loop and the text  
> twice.

imho it is a bit ugly, but if being able to see the compiler command
lines requires slightly ugly output, I'd rather have the ugly output.
(i'd prefer it even more with a proper option that hides the internal
build system logic and the lines like "CC foo.c" and just prints the
command invocations..)

if people are tracking down a build problem, or if they're grepping
logs from a bulk build looking for something, or even the simple case
of making sure CC/CFLAGS are honoured, full command lines are often
invaluable.



Re: UPDATE: gnash 0.8.4

2009-01-12 Thread David Coppa
On Mon, Jan 12, 2009 at 3:57 PM, Stuart Henderson  wrote:
> On 2009/01/12 11:40, David Coppa wrote:
>> Hi,
>> Here is an update to gnash from 0.8.3 to 0.8.4.
>> Please test.
>
> this diff breaks lib-depends-check. also apparently media support is
> worse in 0.8.4 than it was in 0.8.3..

Yes, it seems to play less movies than 0.8.3 (tested on youtube). But
video is smoother for the ones that work.

bye
-david-



Re: UPDATE: mcs and mowgli

2009-01-12 Thread Jonathan Schleifer

Am 12.01.2009 um 16:14 schrieb Federico G. Schwindt:


I don't know others, but as developer I would never prefer colorful
output over the real one, and I don't find it very useful, neither  
for me

nor for anyone who might need to report issues during building.


Well, you see the compiler and linker flags if you look at the  
Makefile. This is usually enough. If those aren't adeded on build for  
some reason, that's a bug in the buildsys - and then you'd need to  
disable .SILENT: :) Normal users should never need to do that, and  
even developers, if they aren't buildsys developers, usually never  
need to do that.



I think as it is with the diff is fine, it's simple and does the job.


I consider that very ugly. You have useless printfs there and also the  
the printfs in the output. So you actually see a loop and the text  
twice.



that's not what you're supposed to use ports, sorry.



Well, I actually like that, as it allows you to have custom patches,  
but still have it tracked via the ports system :). On a new version,  
out-of-date lists it and I can apply the patch to the new version and  
build it :). And I can deinstall it cleanly and already have the  
OpenBSD patches in it :).


--
Jonathan



PGP.sig
Description: Signierter Teil der Nachricht


Re: UPDATE: mcs and mowgli

2009-01-12 Thread Federico G. Schwindt
On Mon, Jan 12, 2009 at 03:49:12PM +0100, Jonathan Schleifer wrote:
> Am 12.01.2009 um 07:33 schrieb Federico G. Schwindt:
>
>> I prefer to have the full output rather than only the ANSI'd version
>> of it (which is quite ugly IMHO).
>
> Would removing the colours work for you?
> If not, I recommend removing the printfs completely. But the plain  
> output will be ugly anyway, as for every target, there is a for i in  
> foo; do. So it will always look ugly ;). That's why there's the coloured 
> output and the full output only for debugging purposes. Even when 
> developing audacious etc., most of the time we keep the .SILENT as 
> usually, I'm the only one who has to remove .SILENT for debugging  
> purposes as I'm the only one developing that build system ;).

  I don't know others, but as developer I would never prefer colorful
output over the real one, and I don't find it very useful, neither for me
nor for anyone who might need to report issues during building.
  I think as it is with the diff is fine, it's simple and does the job.

> [..]
>> Whenever mowgli and mcs switch to use it, we'll pick it up, but for  
>> now
>> commenting one line is better, unless there is a very good reason not 
>> to.
>
> Well, I don't know how others use ports, but I often do just "make"  
> inside the port, change some files and "make" again. This might break  
> it, well, better say it will if I change any headers. I'd need to cd to 
> the work dir then, type make clean there and then type make in the port 
> dir again. Dependency generation is there for a reason ;).

  that's not what you're supposed to use ports, sorry.

  f.-



Re: UPDATE: gnash 0.8.4

2009-01-12 Thread Stuart Henderson
On 2009/01/12 11:40, David Coppa wrote:
> Hi,
> Here is an update to gnash from 0.8.3 to 0.8.4.
> Please test.

this diff breaks lib-depends-check. also apparently media support is
worse in 0.8.4 than it was in 0.8.3..



Re: UPDATE: mcs and mowgli

2009-01-12 Thread Jonathan Schleifer

Am 12.01.2009 um 07:33 schrieb Federico G. Schwindt:


I prefer to have the full output rather than only the ANSI'd version
of it (which is quite ugly IMHO).


Would removing the colours work for you?
If not, I recommend removing the printfs completely. But the plain  
output will be ugly anyway, as for every target, there is a for i in  
foo; do. So it will always look ugly ;). That's why there's the  
coloured output and the full output only for debugging purposes. Even  
when developing audacious etc., most of the time we keep the .SILENT  
as usually, I'm the only one who has to remove .SILENT for debugging  
purposes as I'm the only one developing that build system ;).


 -include is GNU make thing, and I don't want to add it to the  
dependencies

when it can be removed with one line diff.


Well, not GNU only. NetBSD has it as well. But as OpenBSD and FreeBSD  
don't have it, it was changed to include (without the minus) and  
the .deps files are generated on ./configure if they're missing.


Whenever mowgli and mcs switch to use it, we'll pick it up, but for  
now
commenting one line is better, unless there is a very good reason  
not to.


Well, I don't know how others use ports, but I often do just "make"  
inside the port, change some files and "make" again. This might break  
it, well, better say it will if I change any headers. I'd need to cd  
to the work dir then, type make clean there and then type make in the  
port dir again. Dependency generation is there for a reason ;).


--
Jonathan



PGP.sig
Description: Signierter Teil der Nachricht


Re: RESUBMIT: sysutils/apcupsd

2009-01-12 Thread Kirill S. Bychkov

On Thu, January 8, 2009 16:59, Vadim Zhukov wrote:
> On 3 January 2009 З. 20:51:40 Kirill S. Bychkov wrote:
>> Hi!
>> This is a resubmit of apcupsd port.
>> Any comments/oks?
>>
>> $ cat pkg/DESCR-main
>> Apcupsd can be used for power mangement and controlling most of APC's
>> UPS models. Apcupsd works with most of APC's Smart-UPS models as well
>> as most simple signalling models such a Back-UPS, and BackUPS-Office.
>> During a power failure, apcupsd will inform the users about the power
>> failure and that a shutdown may occur. If power is not restored, a
>> system shutdown will follow when the battery is exhausted, a timeout
>> (seconds) expires, or runtime expires based on internal APC
>> calculations determined by power consumption rates.
>
> Still works for me on i386 with BackUPS CS 500VA.
>
> --
>   Best wishes,
> Vadim Zhukov
>
Any other OKs?


-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments



Re: RESUBMIT: sysutils/apcupsd

2009-01-12 Thread Kirill S. Bychkov

On Thu, January 8, 2009 00:45, Stuart Henderson wrote:
> On 2009/01/07 13:31, Aaron Stellman wrote:
>> On Wed, Jan 07, 2009 at 09:59:37PM +0100, Toni Mueller wrote:
>> >
>> > Hi,
>> >
>> > On Sat, 03.01.2009 at 20:51:40 +0300, Kirill S. Bychkov
>>  wrote:
>> > > This is a resubmit of apcupsd port.
>> > > Any comments/oks?
>> >
>> > I have no comment on the port, just a question: What would be the
>> > advantage of using apcupsd in favour of nut?
>>
>> Lacking advantage over nut is not a valid reason why apcupsd shouldn't
>> be imported to ports. There are multiple ports in the tree that do
>> redundant tasks -- it's a matter of choice. I used to use apcupsd myself,
>> and was forced to adopt nut. I don't regret it in any way.
>
> The forerunner to this is already in-tree. The name changed slightly
> (removed a -) but I don't see why we shouldn't just keep the old name
> so that existing users can upgrade to it with pkg_add -u.

Hi. Because they are incompatible. And you can think about apc-upsd and
apcupsd like two different programs.

BTW, is anyone still using apc-upsd?

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments



new: audio/zynaddsubfx

2009-01-12 Thread Jacob Meuser
DESCR:
ZynAddSubFX is a pure software synthesizer that uses no samples.  It
includes many beautiful sounding predefined instruments.  These
instruments can be modified in numerous ways, and/or completely new
instruments can be built.


this is quite different than audio/fluidsynth which is a SoundFont
based (and thus sample based) synthesizer.  the "instruments" in
ZynAddSubFX are also much more tweakable.

it really does make some nice and/or interesting sounds.

it has a virtual keyboard that can be played with a mouse, it can
be played with a computer keyboard, or it can use MIDI input.

includes only a sndio backend.  the jack backend is somewhat broken,
so I did not include it.

-- 
jake...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org


zynaddsubfx-2.2.1-port.tgz
Description: application/tar-gz


UPDATE: gnash 0.8.4

2009-01-12 Thread David Coppa
Hi,
Here is an update to gnash from 0.8.3 to 0.8.4.
Please test.
If it's ok, can this come in?

Regards
-david-

--- MakefileTue Jul 29 20:46:08 2008
+++ MakefileThu Dec 25 08:44:34 2008
@@ -3,9 +3,9 @@
 
 COMMENT=   flash player with firefox browser plugin
 
-VER=   0.8.3
+VER=   0.8.4
 DISTNAME=  gnash-${VER}
-PKGNAME=   ${DISTNAME}p1
+PKGNAME=   ${DISTNAME}
 
 CATEGORIES=www
 MASTER_SITES=  http://getgnash.org/packages/releases/
--- distinfoSat Jun 28 17:46:33 2008
+++ distinfoThu Dec 25 08:41:31 2008
@@ -1,5 +1,5 @@
-MD5 (gnash-0.8.3.tar.gz) = Emvoezhmq916nqMvy0Q2Pg==
-RMD160 (gnash-0.8.3.tar.gz) = rR/1kwmTFGF0WeUtiK7SI0jmHjI=
-SHA1 (gnash-0.8.3.tar.gz) = yaqdr0TKClcjSyOVJfVRtj1ZedA=
-SHA256 (gnash-0.8.3.tar.gz) = dDAQrTkjJL6r5BiGkKuIPtVsYL6nKXjT8hDqnHMWqFM=
-SIZE (gnash-0.8.3.tar.gz) = 4002062
+MD5 (gnash-0.8.4.tar.gz) = 3100e8d669795c03167a171937897c83
+RMD160 (gnash-0.8.4.tar.gz) = f437d24dbe6658961346347d284d1c841a7d50fb
+SHA1 (gnash-0.8.4.tar.gz) = c64e8e86026d281aa8dcd824d68b86ca5e13b539
+SHA256 (gnash-0.8.4.tar.gz) = 
0a4b96cd586fdff717c76f254a7a5a3688d348469f08c5d70b31d7a42590
+SIZE (gnash-0.8.4.tar.gz) = 3987726
--- patches/patch-gnashconfig_h_in  Thu Jan  1 01:00:00 1970
+++ patches/patch-gnashconfig_h_in  Tue Jan 13 20:21:07 2009
@@ -0,0 +1,11 @@
+--- gnashconfig.h.in.orig  Tue Jan 13 20:19:36 2009
 gnashconfig.h.in   Tue Jan 13 20:20:15 2009
+@@ -396,7 +396,7 @@
+ #undef HAVE_STDIO_H
+ 
+ /* Define to 1 if you have the  header file. */
+-#undef HAVE_STDLIB_H
++/* #undef HAVE_STDLIB_H */
+ 
+ /* Define to 1 if you have the `strchr' function. */
+ #undef HAVE_STRCHR
--- patches/patch-libcore_as_value_hThu Jan  1 01:00:00 1970
+++ patches/patch-libcore_as_value_hTue Jan 13 19:35:20 2009
@@ -0,0 +1,24 @@
+--- libcore/as_value.h.origTue Jan 13 19:32:08 2009
 libcore/as_value.h Tue Jan 13 19:34:29 2009
+@@ -64,6 +64,7 @@
+ 
+ // The following template works just like its C counterpart, with added
+ // type safety (i.e., they will only compile for floating point arguments).
++#ifndef isnan
+ template 
+ inline bool
+ isNaN(const T& num, typename boost::enable_if 
>::type* dummy = 0)
+@@ -71,8 +72,13 @@
+   UNUSED(dummy);
+   return num != num;
+ }
++#else
++#define isNaN(x) isnan(x)
++#endif
+ 
++#ifndef isinf
+ #define isinf(x) (isNaN(x - x))
++#endif
+ 
+ /// Use this methods to obtain a properly-formatted property name
+ /// The methods will convert the name to lowercase if the current VM target
--- patches/patch-server_as_value_h Tue Jul 29 20:46:08 2008
+++ patches/patch-server_as_value_h Thu Jan  1 01:00:00 1970
@@ -1,23 +0,0 @@
-$OpenBSD: patch-server_as_value_h,v 1.1 2008/07/29 18:46:08 martynas Exp $
 server/as_value.h.orig Tue Jul 29 01:25:32 2008
-+++ server/as_value.h  Tue Jul 29 01:25:34 2008
-@@ -65,6 +65,7 @@ class asName;
- // The following template works just like its C counterpart, with added
- // type safety (i.e., they will only compile for floating point arguments).
- 
-+#ifndef isnan
- template 
- inline bool
- isnan(const T& num, typename boost::enable_if 
>::type* dummy = 0)
-@@ -72,8 +73,11 @@ isnan(const T& num, typename boost::enable_if(len / GST_MSECOND);
-@@ -249,7 +249,7 @@ SoundGst::getPosition()
-   if (!_pipeline) return 0;
- 
-   GstFormat fmt = GST_FORMAT_TIME;
--  boost::int64_t pos;
-+  gint64 pos;
-   GstStateChangeReturn ret;
-   GstState current, pending;
- 
--- pkg/PLIST   Sat Jun 28 17:46:33 2008
+++ pkg/PLIST   Tue Jan 13 19:48:47 2009
@@ -16,9 +16,9 @@
 lib/gnash/libgnashmedia.so
 lib/gnash/libgnashnet.la
 @lib lib/gnash/libgnashnet.so.${LIBgnashnet_VERSION}
-lib/gnash/libgnashserver-${VER}.so
-lib/gnash/libgnashserver.la
-lib/gnash/libgnashserver.so
+lib/gnash/libgnashcore-${VER}.so
+lib/gnash/libgnashcore.la
+lib/gnash/libgnashcore.so
 lib/gnash/libmozsdk.la
 @lib lib/gnash/libmozsdk.so.${LIBmozsdk_VERSION}
 lib/mozilla-plugins/

gnash.tar.gz
Description: Binary data