On Jul 29, 2008, at 2:46 PM, Martin Krischik wrote:
I thought I could solve the bzip problem by myself - but I guess I was mistaken:
I didn't really understand your previous message ... are you writing a new portfile? If so, you probably want the dev list and not the users list.
MacPorts already knows how to handle tar.bz2 archives (set use_bzip2 yes in the portfile).
Error: Target org.macports.extract returned: invalid command name "/ usr/bin/bzip2"Now, usr/bin/bzip2 is of course an existing executable. So why is it not executed?
Portfiles are not shell scripts (they're tcl scripts), so they don't work the way you are expecting them to.
I have attached the portfile. It's in experimental stage of course - some string-literals need to replaced with variables - which I will do once the thing works.And please don't RTFM me - because I did RTFM - at least the one I found. Of corse if there in another manual I did not find I am all in for it.
Well, you should read the guide (http://guide.macports.org/ and the portfile manpage `man portfile`) to start.
-- Daniel J. Luke +========================================================+ | *---------------- [EMAIL PROTECTED] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
