Bug#512777: Upstream --enable-libabiword violates Debian Policy §10.2

2009-10-28 Thread Patrik Fimml
Hi Jonas, On Mon, Oct 26, 2009 at 02:31:59PM +0100, Jonas Smedegaard wrote: On Mon, Oct 26, 2009 at 01:45:43PM +0100, Patrik Fimml wrote: As a result of the mentioned discussion, I did some packaging work too in July 2009, starting the repository from scratch, following some of the

Bug#512777: Upstream --enable-libabiword violates Debian Policy §10.2

2009-10-26 Thread Patrik Fimml
Hey, I think we've encountered each other some while ago in a discussion with mhatta about repackaging abiword using a git repository (which seems to have died). On Sun, Oct 25, 2009 at 02:45:23PM +0100, Jonas Smedegaard wrote: Just adding the configure option --enable-libabiword is not

Bug#512777: Upstream --enable-libabiword violates Debian Policy §10.2

2009-10-26 Thread Jonas Smedegaard
Hi Patrik, and others following this issue, On Mon, Oct 26, 2009 at 01:45:43PM +0100, Patrik Fimml wrote: Note that upstream doesn't track ABI changes through SONAME, which would further complicate the packaging of libabiword. Yes, I am aware of this. Thanks for bringing it up here, though.

Bug#512777: Upstream --enable-libabiword violates Debian Policy §10.2

2009-10-25 Thread Jonas Smedegaard
Hi, Just adding the configure option --enable-libabiword is not sufficient for official Debian packaging, as the resulting library is too simplisticly built, not handling -fPIC flags and recompiling without -fPIC for a static .a file as required by Debian Policy §10.2. Upstream seems to be