Hi Andreas,
>> Unfortunately there is no other possibility than installing >> libaqbanking20-plugins-qt, which is a recommends of libaqbanking20. >> You ignored this recommendation, thus this bug isn't of severity grave. > > Ok, but then QBankManager should depend on the -qt package, after all > its completely useless without it. I totally agree. I will fix that in the next upload. >>> Probably the plugins should only be recommends, or there should be a >>> virtual libaqbanking20-plugin package which is provided by any of the >>> plugin packages and libaqbanking20-plugins-qt should only depend on >>> the virtual package. >> >> There is no choice any more of what AqBanking backends will be installed >> and what not. The only choice left is: Do you want the Qt support stuff >> (package libaqbanking20-plugins-qt) or not (libaqbanking20-plugins). >> >> This has changed since AqBanking 2.x's packages because it was much more >> work to package with very little gain. > > I find that rather bad. Your forcing stuff on people they don't use or > want to use and thus clutter their system. Currently its just 1 plugin > more to install (and another library which this plugin needs), but if > the other plugins are ported at some point its going to get on my > nerves. > > And I haven't built a debian package for ages, but isn't it just a 2 or > 3 files to "maintain", which contain the list of files for each binary > package you build from a source package and also a proper control file? > Sorry, but I don't find that so much work, after all the list of files > doesn't change with every release of AqBanking. The main problem is to decide what file belongs into what package. If you're going to provide such a list and can grant that no files are missing if a subset of all files aren't installed (because the corresponding package isn't installed) I will probably change my mind. Otherwise I am simply tired doing this error prone (this is my experience) job on my own. Really, I appreciate any help! Regards Micha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
