I demand that Reinhard Tartler may or may not have written... > Josselin Mouette <[EMAIL PROTECTED]> writes: >> libxine1 currently recommends libxine1-doc. However the API documentation >> package is of no use to someone using an application built against >> libxine.
True, but xine(5), which you appear to have completely failed to notice, is. Guess which package it's in :-) The information in xine(5) used to be in xine(1) (xine-ui), which is inappropriate since the information contained therein is relevant regardless of front end - it describes MRL syntax, which users will need if they use the command line, edit playlists etc. The reason for this is when xine-lib 1.2 (eventually) appears, whether in release or development snapshot form, it'll also contain xine(5); as such, the -doc packages either need to conflict or we need libxine-doc. This conflicting is also appropriate wrt the API docs, which were previously packaged as part of libxine1 and would cause the same problem with libxine2. > Agreed, will be fixed in next upload How do you intend to fix it? -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. Don't force it; use a bigger hammer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
