-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-05-23 00:59, Hans-Christoph Steiner wrote: > > Would it make sense to also add the versions since it won't build with > the 'puredata' package 0.43 or newer, something like: > > puredata-dev | puredata << 0.43
i believe this is a bug in the packaging, and is fixed in current git (solution: make "puredata" _depend_ on "puredata-dev" as well) i was only waiting to ping paul to upload the package, but afaik he is currently on a sailing trip. > > Also about puredata-core, it has a menu item set by puredata-core.menu. > That means that you could have puredata-core installed without the GUI, > but having it launched from the Menu. Since the .desktop file is > puredata.desktop, I propose moving the .menu item to puredata.menu > also. I think it would be confusing and not useful to have a menu item > that used to launch a GUI, but now might launch something that might not > have a GUI. right now "puredata" does not provide any files itself, only dependencies to it's sub-packages. lintian will not like it, if there is a binary in the .menu/.desktop files that is not provided by the package itself. given the dependency structure, we could do a lintian override though. i'm wondering whether it wouldn't be better to put the menu into puredata-gui and launch pd-gui instead. > > About puredata-extra, I am planning on making the 'pdextended' package > "Recommend: puredata-extra" instead of including the same source and > binaries. Would it be ok to change the Depends: for puredata-extra to: > > puredata-core (= ${binary:Version}) | pd > hmm, the split is mainly there because you elaborated on having extra/ separately. what made you change your mind? apart from that: puredata-extra would have to be reworked into pd-extra, in order to make it useable by "pd" without breaking the pd vs puredata separation. (if you want to make pdx search objects in /usr/lib/puredata/extra, then we could have simply left everything in /usr/lib/pd/) furthermore: i think that the above depends stanza sounds like a bad idea, as it would allow to have puredata-extra_0.43.0-4 to be installed with either exactly puredata-core_0.43.0-4 or with pdextended-0.39.4-1; so if we change, i think it should be: > Depends: pd finally: actually there is no need to fuddle around with the dependencies. if "pdextended" _recommends_ "puredata-extra", you can install pdextended just fine, even with puredata-extra. puredata-extra would pull in some more dependencies (that is: puredata-core) but i guess that pdextended will by default pull in a thousand packages anyhow :-) fmas IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3bZf4ACgkQkX2Xpv6ydvRSAACgnMIv4zUn0b2b6AmNtmh5+60E HLwAn2i8Y0BAx/YBN37ptyoqizNsZ+oH =/Fc4 -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers