Debian Developers - Subversion / swig1.3

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > October 2004 > Subversion / swig1.3





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Subversion / swig1.3
Philipp Hug

2004-10-26, 7:47 am

subversion depends on swig >= 1.3.22-2 which is in unstable. but it's not in
testing yet because swig cannot be put into testing because it would break
subversion 1.0.6-2 ;-)
did I miss something or is this just a bug in the testing script and needs
manual hinting?

philipp


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Frank Lichtenheld

2004-10-26, 5:51 pm

On Tue, Oct 26, 2004 at 01:39:15PM +0200, Philipp Hug wrote:
> subversion depends on swig >= 1.3.22-2 which is in unstable. but it's not
> in testing yet because swig cannot be put into testing because it would
> break subversion 1.0.6-2 ;-)
> did I miss something or is this just a bug in the testing script and needs
> manual hinting?


Yes, it needs manual hinting and we're aware of this. But it needs to
wait for libhid anyway (two days), so there is no hurry to install the
necessary hint.

Gruesse,
--
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
John Lenz

2004-10-26, 5:51 pm

On 10/26/04 16:35:35, Frank Lichtenheld wrote:
> On Tue, Oct 26, 2004 at 01:39:15PM +0200, Philipp Hug wrote:
> not
> needs
>
> Yes, it needs manual hinting and we're aware of this. But it needs to
> wait for libhid anyway (two days), so there is no hurry to install the
> necessary hint.


I am a swig developer lurking on this list. Building the SWIG runtime
library (which is what causes subversion to depend on SWIG) has been
depreciated since 1.3.20, which was released almost a year ago. About a
week ago, I removed the ability to build the runtime libraries in SWIG CVS,
and so in the next version (1.3.23) you will not be able to build them at
all. We are planning for a release in a week or two.

I am not sure how this will impact debian, but I would seriously encourage
you to build the Python swig wrappers and every other package that depends
on libswigruntime so they don't require the runtime library, and then
remove that library. The runtime library leads to several bugs and
problems, and if those get reported after sarge is released... I am
actually surprised to learn people are still using runtime libraries. You
can completly remove libswig*.so and not lose any functionality, and avoid
a whole bunch of potential bugs.

John


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Adeodato Simó

2004-10-28, 7:49 am

* John Lenz [Tue, 26 Oct 2004 23:02:43 +0000]:
> On 10/26/04 16:35:35, Frank Lichtenheld wrote:
[vbcol=seagreen]
[vbcol=seagreen]
> I am a swig developer lurking on this list. Building the SWIG runtime
> library (which is what causes subversion to depend on SWIG) has been
> depreciated since 1.3.20, which was released almost a year ago. About a
> week ago, I removed the ability to build the runtime libraries in SWIG CVS,
> and so in the next version (1.3.23) you will not be able to build them at
> all. We are planning for a release in a week or two.


I am forwarding this information to the subversion maintainer(s), just
to make sure it doesn't get lost.

> I am not sure how this will impact debian, but I would seriously encourage
> you to build the Python swig wrappers and every other package that depends
> on libswigruntime so they don't require the runtime library, and then
> remove that library. The runtime library leads to several bugs and
> problems, and if those get reported after sarge is released... I am
> actually surprised to learn people are still using runtime libraries. You
> can completly remove libswig*.so and not lose any functionality, and avoid
> a whole bunch of potential bugs.


> John




--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

Arguing with an engineer is like wrestling with a pig in mud: after a
while, you realize the pig is enjoying it.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2009 webservertalk.com