request sponsor/upload for pd-pdstring

Roman Haefeli reduzent at gmail.com
Mon Oct 3 09:50:07 UTC 2011


On Fri, 2011-09-30 at 13:24 +0200, IOhannes m zmölnig wrote:

> debian/control:
>  Depends on "pd",but there "pd" is only a virtual package, and you
> should provide a real one first.
> this is also caught by lintian:
> W: pd-pdstring: virtual-package-depends-without-real-package-depends
> depends: pd
> something like this should fix the problem:
> Depends: puredata-core | pd

I followed the suggestion and lintian did not complain anymore. I
removed all the puredata/pd related packages from my unstable test
system and tried to install the resulting pd-pdstring package with gdebi
and got this:

$ sudo gdebi pbuilder/sid_result/pd-pdstring_0.10.2-1_amd64.deb 
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Building data structures... Done 
Building data structures... Done 
This package is uninstallable
Dependency is not satisfiable: pd

When I change the dependency for pd-pdstring to 'puredata | pd', it
installs fine by installing puredata.

I noticed that only the package 'puredata' provides the virtual package
'pd', but 'puredata-core' does not. 

So, what is the correct setup meant to be? Assuming that pd-libs are
running fine with only the core of Pd, shouldn't 'puredata-core' provide
'pd'?  Or is intended behavior that installing any pd-lib installs the
full 'puredata' suite?

Or asked more generally:
What is the common practice: depending on the least necessary or
depending on then most common setup (whatever that is)?

Roman




More information about the pkg-multimedia-maintainers mailing list