Re: [Fink-devel] stylebook compile failure

2006-01-04 Thread Alexander K. Hansen
On 1/4/06, Alexander K. Hansen <[EMAIL PROTECTED]> wrote: > On 1/4/06, William Scott <[EMAIL PROTECTED]> wrote: > > It hangs (G4, Xcode 2.1, everything up to date, I'm doing this > > remotely): > > > > + java org.apache.stylebook.StyleBook targetDirectory=docs > > book.xml ../styles/apachexml > > [

Re: [Fink-devel] stylebook compile failure

2006-01-04 Thread Alexander K. Hansen
On 1/4/06, William Scott <[EMAIL PROTECTED]> wrote: > It hangs (G4, Xcode 2.1, everything up to date, I'm doing this > remotely): > > + java org.apache.stylebook.StyleBook targetDirectory=docs > book.xml ../styles/apachexml > [StyleBook] Overriding targetDirectory="docs" (Old=".") > [StyleBook] Pro

[Fink-devel] Fink Commander weirdness

2006-01-04 Thread Rogue Marechal
quite minor. I just noticed that a couple - well 5 actually: giftd, opennms, pfamserver, sleepnow and wwwblast - are wrongly marked as unmaintained in Fink Commander. I checked the info files and I can see no reason for that... surely enough 'fink describe' yields expected results so it seems to b

Re: [Fink-devel] compface help with patch

2006-01-04 Thread Charles Lepple
On 1/3/06, Rogue Marechal <[EMAIL PROTECTED]> wrote: > For a start I am getting a fuzz warning of 1. I read and reread the man > page and I more or less understand what that means but still I can't find > the offending spot. I guess finding it would help clear out a lot of > things. [Note: I just

[Fink-devel] stylebook compile failure

2006-01-04 Thread William Scott
It hangs (G4, Xcode 2.1, everything up to date, I'm doing this remotely): + java org.apache.stylebook.StyleBook targetDirectory=docs book.xml ../styles/apachexml [StyleBook] Overriding targetDirectory="docs" (Old=".") [StyleBook] Project URL: "sbk:/sources/book.xml" [BasicEngine] Initializin

Re: [Fink-devel] Re: Use of explicit interpretters in packaging scripts

2006-01-04 Thread Jean-François Mertens
On 04 Jan 2006, at 18:22, Daniel E. Macks wrote: Trevor Harmon <[EMAIL PROTECTED]> said: On Jan 4, 2006, at 2:22 AM, Daniel Macks wrote: If you specify an explicit interpretter in a PatchScript, CompileScript, or InstallScript (i.e, the first line of the field begins with #!), please always

Re: [Fink-devel] Re: Compilation of neon24 with gcc 4.0.1

2006-01-04 Thread David R. Morrison
On Jan 4, 2006, at 9:30 AM, Christian Schaffner wrote: hi Charlie On 03.01.2006, at 17:28, Charles Curry wrote: I assume there is nothing wrong with compiling neon24 with gcc 4.0.1, but the current package being distributed through Fink mirrors seems to prevent this. Might you be able to s

[Fink-devel] Re: Compilation of neon24 with gcc 4.0.1

2006-01-04 Thread Christian Schaffner
hi Charlie On 03.01.2006, at 17:28, Charles Curry wrote: I assume there is nothing wrong with compiling neon24 with gcc 4.0.1, but the current package being distributed through Fink mirrors seems to prevent this. Might you be able to send me a quick fix, either user-edited or patched, to allow

[Fink-devel] Re: Use of explicit interpretters in packaging scripts

2006-01-04 Thread Daniel E. Macks
Trevor Harmon <[EMAIL PROTECTED]> said: > On Jan 4, 2006, at 2:22 AM, Daniel Macks wrote: >> >> If you specify an explicit interpretter in a PatchScript, >> CompileScript, or InstallScript (i.e, the first line of the field >> begins with #!), please always pass the "-e" flag to that shell. > > How

Re: [Fink-devel] Use of explicit interpretters in packaging scripts

2006-01-04 Thread Trevor Harmon
On Jan 4, 2006, at 2:22 AM, Daniel Macks wrote: If you specify an explicit interpretter in a PatchScript, CompileScript, or InstallScript (i.e, the first line of the field begins with #!), please always pass the "-e" flag to that shell. How about making this the default behavior? When processi

[Fink-devel] Use of explicit interpretters in packaging scripts

2006-01-04 Thread Daniel Macks
If you specify an explicit interpretter in a PatchScript, CompileScript, or InstallScript (i.e, the first line of the field begins with #!), please always pass the "-e" flag to that shell. Without this flag, an error during one of the shell commands in the field does not cause the package building