Your message dated Thu, 07 Jun 2007 21:20:30 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427902: ladspa-sdk: Supply source for plugins
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: ladspa-sdk
Version: 1.1-6
Severity: normal

The source for the plugins should be supplied (in this package, not
just the source package), as that is a large part of the point of
them!

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ladspa-sdk depends on:
ii  libc6                   2.5-9+b1         GNU C Library: Shared libraries
ii  libgcc1                 1:4.2-20070528-1 GCC support library
ii  libstdc++6              4.2-20070528-1   The GNU Standard C++ Library v3

ladspa-sdk recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
At Thu, 7 Jun 2007 13:58:17 +0200 (CEST),
Reuben Thomas wrote:
> 
> On Thu, 7 Jun 2007, Junichi Uekawa wrote:
> 
> > Hi
> >
> >> The source for the plugins should be supplied (in this package, not
> >> just the source package), as that is a large part of the point of
> >> them!
> >
> >
> > You can apt-get source the package.
> >
> > There is no point in bloating the binary package with source. This
> > package serves as a central point for 'ladspa.h' header file for
> > package building, and provides some useful basic diagnosis tools. Not
> > everybody is writing a LADSPA plugin...
> 
> The package is called an "SDK". Example source code is usually part of an 
> SDK. If you want to provide a ladspa-dev and a ladspa-sdk package, that's 
> fine, but at the moment it seems to be more than you need for building 
> plugins, but less than you need for writing them.


NAK.

--- End Message ---

Reply via email to