[DRE-maint] Bug#560541: Bug#560541: pkgconfig file in libsvm-dev? [was: Bug#560541: libsvm-ruby: FTBFS]
cilibrar at gmail.com
Tue Dec 15 14:13:00 UTC 2009
I am planning on abandoning libsvm-ruby like I orphaned the libsvm
package. In my opinion there is little chance for the upstream
packaging to be improved in LIBSVM as I have been trying to convince
upstream to do certain improvements for years and they resisted. Now
I am reducing my investment in LIBSVM related technology to 0. Best
On Tue, Dec 15, 2009 at 5:55 AM, Michael Schutte <michi at uiae.at> wrote:
> On Tue, Dec 15, 2009 at 09:27:44AM +0800, Chen-Tse Tsai wrote:
>> Sorry for the inconvenience.
>> This is because we think libsvm is only a simple library(one header and one
>> also we want to keep it as simple as possible and as close to upstream as
>> If it causes too many inconvenience, I will consider to re-introduce it
>> Thanks for your suggestion.
> Ah, I see, so the pkgconfig file is a Debian-specific addition. In this
> case, the upstream version of libsvm-ruby also shouldn’t depend on the
> libsvm.pc file being available.
> I’d just go ahead and change libsvm-ruby’s extconf.rb to set $CFLAGS and
> $LDFLAGS instead of using pkgconfig. Rudi, what is your opinion as
> Debian and upstream maintainer?
> Michael Schutte <michi at uiae.at>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> -----END PGP SIGNATURE-----
> Pkg-ruby-extras-maintainers mailing list
> Pkg-ruby-extras-maintainers at lists.alioth.debian.org
Git, Hg (Mercurial), and Subversion (svn) hosting over SSH
More information about the Pkg-ruby-extras-maintainers