Bug#386652: Incomplete job

2008-02-06 Thread Tuncer Ayaz
On Feb 5, 2008 4:35 PM, Tuncer Ayaz <[EMAIL PROTECTED]> wrote: > Just out of curiosity, would the following change break anything? > --- configure.orig 2008-01-25 10:55:34.0 +0100 > +++ configure 2008-01-25 10:56:14.0 +0100 > @@ -4345,7 +4345,7 @@ > test "$svn_all

Bug#386652: Incomplete job

2008-02-05 Thread Tuncer Ayaz
Just out of curiosity, would the following change break anything? --- configure.orig 2008-01-25 10:55:34.0 +0100 +++ configure 2008-01-25 10:56:14.0 +0100 @@ -4345,7 +4345,7 @@ test "$svn_allowed_neon" = "any"; then svn_allowed_neon_on_system="yes"

Bug#386652: Incomplete job

2007-11-20 Thread C. Michael Pilato
[Peter Samuelson] > Yeah, well ... the --la-file option itself is a poor interface. The > very existence of a ".la file" should be a libtool implementation > detail that libraries and applications never need to know about. They > should be asking "what do I add to my link line to link to neon", n

Bug#386652: Incomplete job

2007-11-20 Thread Peter Samuelson
[C. Michael Pilato] > I'm pretty confident that when you removed the .la file from the > package, you should have also caused 'neon-config --la-file' to stop > claiming that callers could find the .la file for neon in a place it > no longer resides. Yeah, well ... the --la-file option itself is a

Bug#386652: Incomplete job

2007-11-20 Thread C. Michael Pilato
I don't know whether or not it's Correct to remove the .la file from the neon package (though I strongly suspect not). However, I'm pretty confident that when you removed the .la file from the package, you should have also caused 'neon-config --la-file' to stop claiming that callers could find the