I demand that Alexandre Rossi may or may not have written...
>> This package appears to need to depend on libxine1-x.
>> I intend to remove the libxine1-x and libxine1-console dependencies from
>> libxine1 once squeeze is released; at that point, this bug will become
>> serious.
> Okay thanks. My code contains a direct fopen on libxine.so.1 so I
> should maybe also depend on libxine1-bin .
No need; generated dependencies are on libxine1, which depends on
libxine1-bin. There are no plans to change this.
>> It is recommended that you make use of dh_xine (supplied by libxine-dev)
>> and have the package depend on ${xine-x:Depends}; that way, no changes
>> (other than, perhaps, some source changes) will be needed once xine-lib
>> 1.2 is released and uploaded to unstable.
> The package interfaces with xine using python-ctypes, thus it does not have
> libxine-dev as a build dependency. Therefore, using dh_xine would need that
> extra build dependency. Should I add that big build dependency only for
> dh_xine or should I compute de dependencies manually (regarding wasting
> buildd time/space/bandwidth, etc) ?
Your call. Since you specifically use libxine1, you may as well just directly
depend on libxine1-x.
(Incidentally, pyxine may be of interest. It's packaged as python-pyxine.)
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + http://www.youmustbejoking.demon.co.uk/ & http://tartarus.org/ds/
Do not count your chickens before they are hatched.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
