Hi Raphael, thank you for your valuable feedback. Please let me elaborate a bit, why I decided to rename the package aqbanking-tool to aqbanking-tools.
You wrote: > On Sun, 09 Dec 2007, Micha Lenk wrote: > > * rename package aqbanking-tool to aqbanking-tools because users might > > want > > to install the old aqbanking-tool, which contains the binary > > aqbanking-tool, which is missing in the current upstream release. > > Fortunately aqbanking-tool and aqbanking-tools have no files in common, > > thus no conflicting/replacing dependencies. > > This looks plain wrong. Fix the new package to provide the features you > want but do not confuse users with two different packages with almost the > same name! The rename is motivated also by another fact: The package contains some more command line utilities, which lets me believe that aqbanking-tools is a better package name than aqbanking-tool is. So, having upstream drop the executable binary aqbanking-tool is not the only motivation to rename the package. And when else would you do a rename, if not when a stay in NEW is necessary anyways due to soname changes? Maybe I should mention the major difference of package aqbanking-tools compared to package aqbanking-tool (the missing binary aqbanking-tool) in the long description. But I have somewhat strong feelings to stick with the package rename, also for reasons given below... > Note that aqbanking-tool will be auto-removed from unstable when this > version is uploaded to unstable. So you're not providing any choice for > users... except to those who already have the aqbanking-tool installed and > which they'll have left-over without any replacement. That's not good at > all. I am totally aware of the problems you mention here, and yes, I am not very confident about the current situation. But for some users the binary aqbanking-tool is of major importance because it's the only command line utility for doing online banking using AqBanking. The new AqBanking 3 doesn't provide the binary aqbanking-tool because the inner concepts have changed a lot (i.e. the job queue isn't managed by the AqBanking library any more, thus applications need to implement it on their own), which need a non-trivial complete rewrite of aqbanking-tool. Unfortunately upstream will not work on this issue until some future features of higher importance (like support for FinTS 3.0 and SECCOS chip cards) are implemented. All this makes me thinking about providing an AqBanking 2 in parallel to AqBanking 3, at least until AqBanking 3 again delivers the command line utility. This older AqBanking 2 would stick to the old package name aqbanking-tool -- and would also provide the binary aqbanking-tool. So, what do you think about my comments? What do you recommend to do in this case? What do you suggest to be done now? How should I proceed with this bug? Regards Micha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
