On Sun, 09 Dec 2007, Micha Lenk wrote: > 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?
I'm not discussing the timeline of the change, I was discussing the motivation of the change. The reasons above are OK IMO. But the lack of upgrade plan for users of aqbanking-tool is not... either you decide that they officially lost the functionnality and make sure user get aqbanking-tools auto-installed, or you're prepared to support aqbanking-tool as a separate source package (building only this package) and you should prepare that in experimental at the same time (ie now!). In any case, you must fix the description of the corresponding packages to make it clear what they are and how they relate. > 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. You have to take that decision early... and you must be sure that you can effectively do that. Are you able to link aqbanking-tool against the libs of the version 3 ? > What do you suggest to be done now? How should I proceed with this bug? Take a decision: - either deprecate aqbanking-tool properly and make it an empty package depending on aqbanking-tools (so that upgrade for users is smooth) - or package it separately if you want to keep it around Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
