Re: NEW: p5-JSON
you need to find some dependencies for this: Warning: prerequisite HTTP::Request 0 not found. Warning: prerequisite HTTP::Response 0 not found. Those are bundled in p5-libwww.
Re: FreeNX: Anyone working on this?
Chris Humphries wrote: Hello, Is anyone working on this? I was told this was desired by marco and so I started looking into it. It seems something that could be useful to me also. I started working on it, yet is someone also. Would be best to gather resources than work on the same thing at the same time :) If no one is working on this, then I will be. There have been some attempts, but all stalled somewhere along the path, afaict. a FreeNX port would really rock though, as this technology gives really amazing results for remote X over slow links, even with bandwidth-hungry applications like firefox or thunderbird. So I can only encourage you to work on a port (and other people to help you once you've something ready for testing). -- Matthieu Herrb
Re: NEW: p5-JSON
There it is. Added dependency www/p5-libwww and removed WWW from DESCR. Please test and report. steven mestdagh wrote: Genadijus Paleckis [2006-07-04, 11:13:05]: Perl binding to JSON (JavaScript Object Notation language) port can be located at http://84.32.40.221/ports/p5-JSON.tar.gz http://www.json.org/ you need to find some dependencies for this: Warning: prerequisite HTTP::Request 0 not found. Warning: prerequisite HTTP::Response 0 not found. remove WWW in DESCR, and fill in MAINTAINER please. steven Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Re: NEW: p5-JSON
There it is.
Added dependency www/p5-libwww and removed WWW from DESCR.
Please test and report.
You should not point $MASTER_SITE_PERL_CPAN to ../../authors/ but
use the group instead. In case of JSON, it's Apache. Hence, you should
have this instead:
MASTER_SITES=${MASTER_SITE_PERL_CPAN:=Apache/}
Re: NEW: p5-JSON
fixed. Sorry, i'll keep that in mind.
Srebrenko Sehic wrote:
There it is.
Added dependency www/p5-libwww and removed WWW from DESCR.
Please test and report.
You should not point $MASTER_SITE_PERL_CPAN to ../../authors/ but
use the group instead. In case of JSON, it's Apache. Hence, you should
have this instead:
MASTER_SITES=${MASTER_SITE_PERL_CPAN:=Apache/}
Re: Hylafax: faxaddmodem stuck at flow control
On Tue, 11 Jul 2006 19:55:44 +0200, Toni Mueller wrote: Hmmm? If the fax is garbled, I suspect that you have flow control problems with your modem. No. That was just quite another item. See below. First, second and third I want to thank 3 nice guys for helping me offline !!! Now to what transpired; FYI: 1. 4.1.5 has a procedural problem to faxsetup and faxaddmodem on recent OpenBSDs. It doesn't go through; observed by others as well. 2. Some unofficial port (or the straightforward make make install) of 4.2.5 or 4.3.0 do go through *if done from scratch* 3. faxaddmodem of 4.2.5 and 4.3.0 will *not* go through on a system that had 4.1.5 installed earlier. 3.a. pkg_delete hylafax leaves a lot of files inclusive the whole /var/spool/hylafax intact. That's from where a faulty variable stems that hinders any faxaddmodem to go through. Therefore 4. in order to get it running, a fresh make make install on a fresh system (or one cleansed from any hyla and fax) of 4.2.5 or 4.3.0 is needed. 5. The EOL error of my out-of-the-box install of original hylafax4.3.0 is completely unrelated: http://www.hylafax.org/archive/2005-12/msg00255.php One might think of setting Class2RecvDataTrigger: \022 in /etc/config.tty0x by default Uwe
nanoblogger port
hello everyone. i created a port for the nanoblogger weblog engine and i would be glad if i could get some hands on it for testing. check the attachment and send feedback. thanks in advance. nanoblogger_port.tar.gz Description: application/tar-gz
Re: Non linear
On 2/23/05, Marc Espie [EMAIL PROTECTED] wrote: On Tue, Feb 22, 2005 at 06:29:25PM -0800, Troy James Sobotka wrote: I see that Cinelerra (http://heroinewarrior.com/cinelerra.php3) has been ported more or less to FreeBSD. Would this application be a viable port to my beloved Open? Looks cool. No-one has looked at it yet, though we do have ports for some components, like OpenEXR now. I've doing up ports for yasm, faac and x264, updated Jacob's libmpeg3 and am working on whatever else might be necessary. I'm still just trying to get all the way throught configure. here's a short list of what it needs so far, based on what's posted in the wiki and the various packages it includes in the distribution. BUILD_DEPENDS= yasm::devel/yasm \ nasm::devel/nasm LIB_DEPENDS=:esound-*:audio/esound \ ::audio/toolame \ a52.0::audio/liba52 \ faac.0::audio/faac \ faad.0::audio/faad \ mp3lame.0::audio/lame \ sndfile.1::audio/libsndfile \ audiofile::devel/libaudiofile \ uuid.12::devel/uuid \ avcodec.7,avutil.1::graphics/ffmpeg \ tiff.35.::graphics/tiff \ x264.47::graphics/x264 \ fftw3.4::math/fftw3 \ dv.4::multimedia/libdv \ mpeg3.0::multimedia/libmpeg3 \ theora.1::multimedia/libtheora \ lavfile.3::multimedia/mjpegtools -- GDB has a 'break' feature; why doesn't it have 'fix' too?
[NEW] x11/ruby-gtk2
GTK+2 Bindings for the ruby language. I only tested it with irb, therefore it needs some more testing with real applications. Please test, commit, and so on. Thanks. -- Jonathan ruby-gtk2.tgz Description: Unix tar archive
Re: nanoblogger port
On Thu, Jul 13, 2006 at 06:54:02PM +0300, Sideris Michael wrote:
hello everyone. i created a port for the nanoblogger weblog engine
and i would be glad if i could get some hands on it for testing.
check the attachment and send feedback. thanks in advance.
Looks fine; works well enough. I know that I had suggested using sed
to change @@PREFIX@@ to whatever ${PREFIX} is set to earlier, but
I'm not sure it's necessary. I think the sed lines in post-extract
should be prepended with '@'.
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Re: nanoblogger port
Removed the nb-wrapper thingie, added a @ on the post-extract sed line and I think that is all more or less. I guess if there is no problem someone can commit it. Thanks in advance. nanoblogger_port.tar.gz Description: application/tar-gz
Re: NEW devel/cflow
On Fri, 14 Jul 2006, steven mestdagh wrote: Louis Bertrand [2006-07-13, 21:39:57]: Hello, I would like to submit a port of cflow-1.1, a C program to analyze C source files and print a call graph. This is not the same as cflow 2.x which is a shell script that uses lex and yacc. It's not as comprehensive as cscope, but I find it useful to start studying a program. Some notes: I'm confused about the distinction between WANTLIB and LIB_DEPENDS. I used WANTLIB for the statically linked libintl (devel/gettext) and libiconv (converters/libiconv). Tested on -current/macppc (July 2) and -current/i386 (July 10). It's my first port. Be gentle. http://www.bertrandtech.ca/cflow-20060712.tar.gz linked from http://www.bertrandtech.ca/openbsd.html looks fairly good. you want to use MODULES=devel/gettext and regenerate the PLIST. (this also takes care of libiconv dependency) I added MODULES and removed LIB_DEPENDS. this isn't building any shared libraries, so why use CONFIGURE_SHARED? I misinterpreted this as use shared libs vs. statically linked. Latest, tested on macppc and i386: http://www.bertrandtech.ca/cflow-20060713.tar.gz Thanks --Louis
NEW: py-ctypes
Hi, Here is a port of the Python ctypes module. ctypes is an advanced ffi (Foreign Function Interface) package for Python 2.3 and higher. ctypes allows to call functions exposed from dlls/shared libraries and has extensive facilities to create, access and manipulate simple and complicated C data types in Python - in other words: wrap libraries in pure Python. It is even possible to implement C callback functions in pure Python This module is going to be a standard part of Python-2.5, and quite a few Python libraries are starting to use it in favour of writing their own interface glue or using swig, etc. Ok? -d py-ctypes.tgz Description: Binary data
vmware in -current
Vmware has been broken in -current for a long time now by the PAE changes. If you have an interest in a working vmware in the next release, and want to try your hand at a hard problem, someone stepping up with a fix would be great. todd@ and mcbride@ should have details, and in fact posting them to the list may be a good idea.
