Re: [Fink-devel] fatback in fink

2004-07-13 Thread Martin Langhoff (NZL)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicholas Harbour has sent me a tar with fatback-1.4 sporting a proper GPL in the COPYING file. Will this sort the problem out? cheers, martin - -- - -- Martin Langhoff http://nzl.com.ar/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4

Re: [Fink-devel] fatback in fink

2004-07-12 Thread Martin Langhoff (NZL)
se it under the GPL. Subterfuge I know, but it worked. | | Nick. | | p.s. You're lucky, I haven't worked here for 2 years and just came back | and got my email account reactivated :) | | -Original Message- | From: Martin Langhoff (NZL) [mailto:[EMAIL PROTECTED] | Sent: Wednesda

Re: [Fink-devel] fatback in fink

2004-07-12 Thread Martin Langhoff (NZL)
statement from the author acknowledging it is invalid, and stating that fatback is wholly covered by the GPL. Did it now make it to the list? I'll forward it now. cheers, martin - -- - -- Martin Langhoff http://nzl.com.ar/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Co

Re: [Fink-devel] fatback in fink

2004-07-07 Thread Martin Langhoff (NZL)
f the | DoD Computer Forensics Lab. <[EMAIL PROTECTED]> cheers, martin - -- - -- Martin Langhoff http://nzl.com.ar/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFA7LP7xMcU+h4F1RYRAq7CAJsGfW7qjOmTWRFVKUL

[Fink-devel] Doc bug - Bad heredoc syntax

2004-06-02 Thread Martin Langhoff
The CustomMirror example shows an incorrect heredoc syntax. It opens with << and closes with >>. Should close with <<. This can be seen at http://fink.sourceforge.net/doc/packaging/reference.php?phpLang=en -- right under the "Unpack Phase" subtitle. regards, martin -- ---

[Fink-devel] Doc bug - Bad heredoc syntax

2004-06-01 Thread Martin Langhoff (NZL)
The CustomMirror example shows an incorrect heredoc syntax. It opens with << and closes with >>. Should close with <<. This can be seen at http://fink.sourceforge.net/doc/packaging/reference.php?phpLang=en -- right under the "Unpack Phase" subtitle. regards,

Re: [Fink-devel] Patch and PatchScript ignored

2004-05-31 Thread Martin Langhoff (NZL)
peed 100 6 100 60 0 3 0 0:00:01 0:00:01 0:00:00 0 You already have the package descriptions from the latest Fink point release. (installed:0.7.0 available:0.7.0) [EMAIL PROTECTED]:~]$ -- -- Martin Langhoff http://nzl.com.ar/ --

Re: [Fink-devel] Policy and apache 1.3.x modules

2004-05-31 Thread Martin Langhoff (NZL)
. BTW, adding new package sources to fink seems to be more complex than on Debian. Strange. You mention some X11 related exceptions. I'd like to know what mechanisms does it use to manage the "outside" files, and I can't find anything about it. regards, martin -- -- Marti

[Fink-devel] Policy and apache 1.3.x modules

2004-05-31 Thread Martin Langhoff (NZL)
which is packaged in four parts: the core midgard library, an Apache module, a PHP extension, and a "data" module. Whatever the solution is, I expect to take the same approach with the PHP extension, as PHP is provided as part of the default OS X install. regards, martin -- --

Re: [Fink-devel] Patch and PatchScript ignored

2004-05-31 Thread Martin Langhoff (NZL)
a fink bug, or should I be changing revision number every attempt during a debugging session? regards, martin -- -- Martin Langhoff http://nzl.com.ar/ --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing e

[Fink-devel] Patch and PatchScript ignored

2004-05-29 Thread Martin Langhoff (NZL)
`sudo fink -v rebuild libapache-mod-midgard` does not mention any patchfiles -- it seems to be ignoring the entries in the info file completely. The .info and .patch files look like: $ cat libapache-mod-midgard.info Package: libapache-mod-midgard Version: 1.5.0 Revision: 1 Maintainer: Martin Lan

[Fink-devel] Busted /etc due to a fink bug?

2004-05-29 Thread Martin Langhoff (NZL)
remove. And that was the last time /etc was seen alive. After a moment of panic, I fixed it mounting the iBook as a FW device -- connected to another mac. Recreated the symlink, easy enough. However, I find distressing that I was able to do this so... effortlessly. m -- -- Martin Langhoff http