Re: package conflict with source package but not with binary package

[Dominik 'Rathann' Mierzejewski]

Hi, Till.

On Saturday, 30 December 2017 at 17:27, Till Hofmann wrote:
[...]
> So, I'm wondering:
> Can I add "Provides: bear = %{version}-%{release}", as bear does not
>
> provide a bear binary package? To me, this seems risky and confusing,
> but it would solve the issue.
> 2. If not, would it make sense to rename the current bear (source)
> package into something else, e.g., bear-factory, so we can use 'bear'
> for the compilation database?

Option 2 makes most sense in light of what you wrote. Thank you for
the thorough research on this matter. If I were the current bear
package maintainer, I'd agree with your reasoning.

Regards,
Dominik