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

2018-01-26 Thread Till Hofmann
On 12/30/2017 09:44 PM, Dominik 'Rathann' Mierzejewski wrote: > Hi, Till. > > On Saturday, 30 December 2017 at 17:27, Till Hofmann wrote: > [...] >> So, I'm wondering: >> 1. Can I add "Provides: bear = %{version}-%{release}", as bear does not >> provide a bear binary package? To me, this seems r

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

2017-12-30 Thread Dominik 'Rathann' Mierzejewski
Hi, Till. On Saturday, 30 December 2017 at 17:27, Till Hofmann wrote: [...] > So, I'm wondering: > 1. 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 m

package conflict with source package but not with binary package

2017-12-30 Thread Till Hofmann
Hi all, I'm preparing Bear [1] as a Fedora package. Unfortunately, the package name bear is already taken by the bear engine [2], so I'm considering the best way to resolve this. Ubuntu [3], Debian [4], Arch (AUR) [5], and Mint [6] all package the compilation database (i.e., the package I'm workin