On Thu, Nov 18, 2010 at 04:40:38PM +0000, Joao Cordeiro wrote: > Zint checks for qt and installs both zint and zint-qt if it is found. > Otherwise, it just installs zint. I don't believe this to be the optimal > approach. Even if I have qt installed, it doesn't necessarily means that I > want zint-qt. Despite that fact, I don't want to package zint with its > original name, installing less stuff than the developer does and more > importantly, removing features to users that installed previous versions of > the package through AUR.
Yes, another problem is that packages might be built and installed on different systems. Even packages from the AUR. > My first idea was to create zint-noqt, implicitly leaving zint-qt behind. Is > this the best way for me to solve this? Correct. Either tell people to remove some line from the PKGBUILD to disable Qt support (if it's a really simple change) or create a separate source package, as you already said.
