> I'm not sure. Historically, dependency generators of this kind don't
> include the architecture information because of the issues related to
> determining whether a package is a noarch package or an archful
> package (or if it needs to transition from one to the other). It's
> somewhat easier to
On Wed, Apr 13, 2016 at 8:43 AM, Miro Hrončok wrote:
>
> Hi, this looks very good.
>
> I tried to build some arched packages and was wondering, if there shouldn't
> be %{?_isa} included at the end of the provide name?
>
> Something like:
>
> Provided form the 64bit package:
>
> python3
On 11.4.2016 05:29, Neal Gompa wrote:
Hello all,
It's been a while since I messaged this list about the new dependency
generator being upstreamed into RPM[0]. Since then, I've taken your
valuable feedback and incorporated it into the version that now sits
in RPM git master[1].
A little bit ago,
Hello all,
It's been a while since I messaged this list about the new dependency
generator being upstreamed into RPM[0]. Since then, I've taken your
valuable feedback and incorporated it into the version that now sits
in RPM git master[1].
A little bit ago, I pushed a package to Copr[2] that incl
