Re: [kde-freebsd] Trouble with KMplayer

2007-11-08 Thread Michael Nottebrock
On Thu, Nov 08, 2007 at 01:54:09AM +0100, Danny Pansters wrote:
> On Wednesday 07 November 2007 02:25:29 Gary Kline wrote:
> > Does anybody know why KMPlayer hangs when I try to play *.ram
> > files?   mplayer handles there fine--at least in my music files.
> > But when I try to listen to files such as found as
> > "thewritersalamac.org", K/mplayer stops..  I set Konq to
> > realplay-10 and it plays.
> >
> > Anybody??
> 
> 
> .ram refers to (ancient term) "Real Audio Meta" file. It's a text file 
> containing the actual media url(s). Looks like (k)mplayer doesn't support 
> these, or maybe it doesn't support it because the media type is .smil 
> (another container format) rather than merely .ra or .rv/.rm, the actual 
> audio/video data files.

mplayer should be able to play these with the -playlist switch. kmplayer would 
need to do some parsing/guessing itself to call mplayer with that parameter. I 
cannot test it right now, but I think it should be able to do that - at least 
the kmplayer-kpart usually works quite well on embedded real media in konqueror.

-- 
   ,_,   | Michael Nottebrock   | [EMAIL PROTECTED]
 (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org 
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


Re: [kde-freebsd] Should graphics/pixieplus still exist?

2007-11-08 Thread Mikhail Teterin
Deafening silence...

Anyway. Attached is the proposed update -- I suspect, the port has not worked 
for /very/ long time. It used to overwrite a kdelibs-installed x-pcx mimelnk 
and install a useless x-tga, when x-targa was already installed by kdelibs.

This and other pkg-plist problems should all be fixed now. The port will 
depend on and use GraphicsMagick instead of ImageMagick. GM's developers 
emphasise API-stability, so the port should stop requiring as frequent 
updates as it used to. Keeping port's own "private" headers is no longer 
necessary either.

Please, approve. Thanks,

-mi

On середа 07 листопад 2007, Mikhail Teterin wrote:
= Hello!
= 
= The port promises experimental features, that are "not yet" available in the 
= base KDE distribution.
= 
= That's according to the upstream web-site:
= 
=   http://www.mosfet.org/pixie/
= 
= However, the most recent version (Pixie-1.02a) on the site is from April
= 2004.
= 
= The version (0.5.4.1) built by the port is a little bit newer:
= 
=   http://people.fruitsalad.org/avleeuwen/distfiles/pixieplus/
=   
= -- February 2005...
= 
= The port no longer builds due to the ever-changing ImageMagick API (the 
= cvs-log is full of fixes due to this moving target -- using GraphicsMagick 
= instead is strongly encouraged, whenever possible, BTW).
= 
= It can be fixed again, but is it worth the trouble? Are the features offered 
= by pixieplus /still/ not available by the KDE itself, or should the port
= just be retired? Maybe, there is a new version somewhere?
= 
= Please, advise -- I'd like to resolve this one way or the other before the 
= currently-prepared OS-releases are cut.
= 
= Thanks!
= 
=   -mi


Index: Makefile
===
RCS file: /home/pcvs/ports/graphics/pixieplus/Makefile,v
retrieving revision 1.25
diff -U2 -r1.25 Makefile
--- Makefile	19 May 2007 20:10:20 -	1.25
+++ Makefile	8 Nov 2007 14:39:25 -
@@ -8,5 +8,5 @@
 PORTNAME=	pixieplus
 PORTVERSION=	0.5.4.1
-PORTREVISION=	8
+PORTREVISION=	9
 CATEGORIES=	graphics kde
 MASTER_SITES=	http://people.fruitsalad.org/avleeuwen/distfiles/${PORTNAME}/
@@ -15,19 +15,26 @@
 COMMENT=	A free, fast, and feature packed image browser and viewer for KDE
 
-LIB_DEPENDS=	Magick.10:${PORTSDIR}/graphics/ImageMagick \
-		ungif.5:${PORTSDIR}/graphics/libungif
+LIB_DEPENDS=	GraphicsMagick:${PORTSDIR}/graphics/GraphicsMagick \
+		ungif:${PORTSDIR}/graphics/libungif
 
 USE_AUTOTOOLS=	libtool:15
-USE_GMAKE=	yes
 USE_KDELIBS_VER=3
 INSTALLS_SHLIB=	yes
 USE_BZIP2=	yes
+ALL_TARGET=	-j`${SYSCTL} -n hw.ncpu`
 
 .include 
 
 post-patch:
-	@${CP} ${FILESDIR}/blob_private.h ${WRKSRC}/app/
-	@${CP} ${FILESDIR}/exception_private.h ${WRKSRC}/app/
-	@${CP} ${FILESDIR}/image_private.h ${WRKSRC}/app/
+	# Massaging to use GraphicsMagick
+	${REINPLACE_CMD} -e	\
+	"s,INCLUDES =.*,INCLUDES=`${LOCALBASE}/bin/GraphicsMagick-config \
+		--cppflags` -I${LOCALBASE}/include," -e	\
+	"s|-lMagick -ltiff|`${LOCALBASE}/bin/GraphicsMagick-config \
+		--libs`|" ${WRKSRC}/app/Makefile.in
+	${REINPLACE_CMD} -e 's,,,'	\
+	${WRKSRC}/app/*.h ${WRKSRC}/app/*.cpp
+	${REINPLACE_CMD} -e s,Magick-config,GraphicsMagick-config,g -e s,6.0.0,1.1.10, \
+	${WRKSRC}/configure
 
 .include 
Index: pkg-plist
===
RCS file: /home/pcvs/ports/graphics/pixieplus/pkg-plist,v
retrieving revision 1.3
diff -U2 -r1.3 pkg-plist
--- pkg-plist	23 Feb 2006 10:37:19 -	1.3
+++ pkg-plist	8 Nov 2007 14:39:25 -
@@ -209,5 +209,4 @@
 share/mimelnk/image/x-xwd.desktop
 share/mimelnk/image/x-miff.desktop
-share/mimelnk/image/x-tga.desktop
 share/mimelnk/image/x-pict.desktop
 share/icons/locolor/22x22/actions/thumb.png
@@ -238,8 +237,8 @@
 share/icons/hicolor/32x32/actions/window_new.png
 share/icons/hicolor/32x32/actions/catagory.png
[EMAIL PROTECTED] share/applnk/Graphics
[EMAIL PROTECTED] share/applnk
[EMAIL PROTECTED] share/apps/konqueror/servicemenus
[EMAIL PROTECTED] share/apps/konqueror
[EMAIL PROTECTED] share/applnk/Graphics
[EMAIL PROTECTED] share/applnk
[EMAIL PROTECTED] share/apps/konqueror/servicemenus
[EMAIL PROTECTED] share/apps/konqueror
 @dirrm share/apps/pixie/doc/en/basic
 @dirrm share/apps/pixie/doc/en/framed
@@ -251,25 +250,25 @@
 @dirrm share/apps/pixie/toolbar
 @dirrm share/apps/pixie
[EMAIL PROTECTED] share/apps
[EMAIL PROTECTED] share/mimelnk/image
[EMAIL PROTECTED] share/mimelnk
[EMAIL PROTECTED] share/icons/locolor/22x22/actions
[EMAIL PROTECTED] share/icons/locolor/22x22
[EMAIL PROTECTED] share/icons/locolor/16x16/apps
[EMAIL PROTECTED] share/icons/locolor/16x16/actions
[EMAIL PROTECTED] share/icons/locolor/16x16
[EMAIL PROTECTED] share/icons/locolor/32x32/actions
[EMAIL PROTECTED] share/icons/locolor/32x32
[EMAIL PROTECTED] share/icons/locolor
[EMAIL PROTECTED] share/icons/hicolor/16x16/actions
[EMAIL PROTECTED] share/icons/hicolor/16x16/apps
[EMAIL PROTECTED] share/icons/hicolor/16x16
[EMAIL PR

Re: [kde-freebsd] Trouble with KMplayer

2007-11-08 Thread Gary Kline
On Thu, Nov 08, 2007 at 10:18:34AM +0100, Michael Nottebrock wrote:
> On Thu, Nov 08, 2007 at 01:54:09AM +0100, Danny Pansters wrote:
> > On Wednesday 07 November 2007 02:25:29 Gary Kline wrote:
> > >   Does anybody know why KMPlayer hangs when I try to play *.ram
> > >   files?   mplayer handles there fine--at least in my music files.
> > >   But when I try to listen to files such as found as
> > >   "thewritersalamac.org", K/mplayer stops..  I set Konq to
> > >   realplay-10 and it plays.
> > >
> > >   Anybody??
> > 
> > 
> > .ram refers to (ancient term) "Real Audio Meta" file. It's a text file 
> > containing the actual media url(s). Looks like (k)mplayer doesn't support 
> > these, or maybe it doesn't support it because the media type is .smil 
> > (another container format) rather than merely .ra or .rv/.rm, the actual 
> > audio/video data files.
> 
> mplayer should be able to play these with the -playlist switch. kmplayer 
> would need to do some parsing/guessing itself to call mplayer with that 
> parameter. I cannot test it right now, but I think it should be able to do 
> that - at least the kmplayer-kpart usually works quite well on embedded real 
> media in konqueror.


Then which things do i click on, or what strings do
i add?  i found the "almanac" site, click on "use
KMplayer", and after several seconds of fumbling,
kmplayer simply hung up.  it stopped.

Otherwise [k]mplayer works on any ttype of args.
...Parsing problem?

gary

> 
> -- 
>,_,   | Michael Nottebrock   | [EMAIL PROTECTED]
>  (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
>\u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org 
> ___
> kde-freebsd mailing list
> kde-freebsd@kde.org
> https://mail.kde.org/mailman/listinfo/kde-freebsd

-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix
  http://jottings.thought.org   http://transfinite.thought.org

___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


Re: [kde-freebsd] Should graphics/pixieplus still exist?

2007-11-08 Thread Mark Linimon
Approved from portmgr if you wish to keep it, or delete it if is seems
best ...

mcl
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


Re: [kde-freebsd] Should graphics/pixieplus still exist?

2007-11-08 Thread Arjan van Leeuwen
I don't use pixieplus anymore, but depending on GraphicsMagick is probably a
good idea. Not sure if there's many people still using pixieplus though.

Thanks,

Arjan

2007/11/8, Mikhail Teterin <[EMAIL PROTECTED]>:
>
> Deafening silence...
>
> Anyway. Attached is the proposed update -- I suspect, the port has not
> worked
> for /very/ long time. It used to overwrite a kdelibs-installed x-pcx
> mimelnk
> and install a useless x-tga, when x-targa was already installed by
> kdelibs.
>
> This and other pkg-plist problems should all be fixed now. The port will
> depend on and use GraphicsMagick instead of ImageMagick. GM's developers
> emphasise API-stability, so the port should stop requiring as frequent
> updates as it used to. Keeping port's own "private" headers is no longer
> necessary either.
>
> Please, approve. Thanks,
>
> -mi
>
> On середа 07 листопад 2007, Mikhail Teterin wrote:
> = Hello!
> =
> = The port promises experimental features, that are "not yet" available in
> the
> = base KDE distribution.
> =
> = That's according to the upstream web-site:
> =
> =   http://www.mosfet.org/pixie/
> =
> = However, the most recent version (Pixie-1.02a) on the site is from April
> = 2004.
> =
> = The version (0.5.4.1) built by the port is a little bit newer:
> =
> =   http://people.fruitsalad.org/avleeuwen/distfiles/pixieplus/
> =
> = -- February 2005...
> =
> = The port no longer builds due to the ever-changing ImageMagick API (the
> = cvs-log is full of fixes due to this moving target -- using
> GraphicsMagick
> = instead is strongly encouraged, whenever possible, BTW).
> =
> = It can be fixed again, but is it worth the trouble? Are the features
> offered
> = by pixieplus /still/ not available by the KDE itself, or should the port
> = just be retired? Maybe, there is a new version somewhere?
> =
> = Please, advise -- I'd like to resolve this one way or the other before
> the
> = currently-prepared OS-releases are cut.
> =
> = Thanks!
> =
> =   -mi
>
>
>
>
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


Re: [kde-freebsd] Should graphics/pixieplus still exist?

2007-11-08 Thread Mikhail Teterin
четвер 08 листопад 2007 01:57 по, Arjan van Leeuwen Ви написали:
> I don't use pixieplus anymore, but depending on GraphicsMagick is probably
> a good idea. Not sure if there's many people still using pixieplus though.

It is in your directory on fruitsalad -- can you browse the web-server logs to 
see, how popular it is?

Regardless, since I already went through the trouble of fixing it up, may as 
well update the port :-) ... Awaiting approval.

 -mi

> Thanks,
>
> Arjan
>
> 2007/11/8, Mikhail Teterin <[EMAIL PROTECTED]>:
> > Deafening silence...
> >
> > Anyway. Attached is the proposed update -- I suspect, the port has not
> > worked
> > for /very/ long time. It used to overwrite a kdelibs-installed x-pcx
> > mimelnk
> > and install a useless x-tga, when x-targa was already installed by
> > kdelibs.
> >
> > This and other pkg-plist problems should all be fixed now. The port will
> > depend on and use GraphicsMagick instead of ImageMagick. GM's developers
> > emphasise API-stability, so the port should stop requiring as frequent
> > updates as it used to. Keeping port's own "private" headers is no longer
> > necessary either.
> >
> > Please, approve. Thanks,
> >
> > -mi
> >
> > On середа 07 листопад 2007, Mikhail Teterin wrote:
> > = Hello!
> > =
> > = The port promises experimental features, that are "not yet" available
> > in the
> > = base KDE distribution.
> > =
> > = That's according to the upstream web-site:
> > =
> > =   http://www.mosfet.org/pixie/
> > =
> > = However, the most recent version (Pixie-1.02a) on the site is from
> > April = 2004.
> > =
> > = The version (0.5.4.1) built by the port is a little bit newer:
> > =
> > =   http://people.fruitsalad.org/avleeuwen/distfiles/pixieplus/
> > =
> > = -- February 2005...
> > =
> > = The port no longer builds due to the ever-changing ImageMagick API (the
> > = cvs-log is full of fixes due to this moving target -- using
> > GraphicsMagick
> > = instead is strongly encouraged, whenever possible, BTW).
> > =
> > = It can be fixed again, but is it worth the trouble? Are the features
> > offered
> > = by pixieplus /still/ not available by the KDE itself, or should the
> > port = just be retired? Maybe, there is a new version somewhere?
> > =
> > = Please, advise -- I'd like to resolve this one way or the other before
> > the
> > = currently-prepared OS-releases are cut.
> > =
> > = Thanks!
> > =
> > =   -mi
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


[kde-freebsd] broken build -- kde3

2007-11-08 Thread Chuck Robey
OK, this set of notes is mostly because I can't find a paper notepad, 
but also because it's probably going to need action by someone dealing 
with the KDE3 ports.  I am going to describe what I was trying to do, 
and what I found in trying to fix it.

I was using portmanager to build things, and the stuff I found most 
often is that, in ports with a largish set of sections that can be 
optioned in, one or more of those options would be broken ... so I would 
see the errors at the termination of the portmanager run, find the port 
that seemed to have foundered on an optional dependency, figure which 
option was giving the kiss of death, and option it out.  Too trivial, I 
thought, to bother you folks with.  The last one I hit was when it 
refused x11/kde3 because it couldn't  build kdemultimedia-3.5.8, which 
couldn't build akode-plugins-polypaudio-2.0.1_1,1 which couldn't build 
polypaudio-0.7_4.  Finally, in polypaudio-0.7_4, it actually had a real 
problem, it couldn't find file polyplib-simple.h.

First off, I located that file using a little script of mine that scans 
the pkg-plists for gold, and that was in polypaudio/, but that port 
failed to install (not ONLY, but mainly) cause of a collision in trying 
to add a new groupname to /etc/group ... but the name of the group that 
was already squatting there was pulse-rt.  A bit more investigation 
showed me that the polypaudio port is deprecated in favor of that new 
pulseaudio port.

OK, the natural thing now was to see if that pulseaudio port supplied 
the include file I was hunting (are you still awake at the end of all 
this??) ... well, it wasn't.  There was another file in the pulseaudio 
port that had an ending of "-simple.h" but the innards were too 
different to serve as a replacement.

OK, I just did a Google on it, and I don't see any traces of a 
pre-existing akode-plugins-pulseaudio port.  That would have been my 
preferred way to go, to change dependencies to need this.  Crap.  OK, 
then I will need to do some surgery to eliminate 
akode-plugins-polypaudio as a dependency.

Well, this is too damn complicated for a PR, and unless someone with 
more time with me can actually write that plugin, then I don't even see 
a better fix.  Maybe whoever reads this is measureably smarter than I 
am.   Good luck to you, whomever you are.

PS.  I hzve lots of disk, and I will keep the builds around for a bit, 
if you wanted to give it a looksee.  Any committers, or folks who can 
show me as least 3 non-trivial ports they did, just send me a ssh line 
if you wanted a login.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd