Re: Package with spec name != packagename.spec

2017-03-06 Thread Jason L Tibbitts III
> "SM" == Sandro Mani writes: SM> So just for curiosity, does the tooling allow an arbitrary name for SM> the specfile and does it just pick the first one it finds when SM> building the SRPM? There is no one "tooling". fedpkg/pyrpkg will try to find the spec named after the package and then

Re: Package with spec name != packagename.spec

2017-03-06 Thread Sandro Mani
On 06.03.2017 17:09, Martin Bříza wrote: On Mon, 06 Mar 2017 17:03:51 +0100, Sandro Mani wrote: Hi I just came across a package (mingw-qt5-qtquickcontrols) whose specfile isn't named .spec (in this case, mingw-qtquickcontrols.spec instead of mingw-qt5-qtquickcontrols.spec). As I unders

Re: Package with spec name != packagename.spec

2017-03-06 Thread Martin Bříza
On Mon, 06 Mar 2017 17:03:51 +0100, Sandro Mani wrote: Hi I just came across a package (mingw-qt5-qtquickcontrols) whose specfile isn't named .spec (in this case, mingw-qtquickcontrols.spec instead of mingw-qt5-qtquickcontrols.spec). As I understand it this is against the guildelines?

Package with spec name != packagename.spec

2017-03-06 Thread Sandro Mani
Hi I just came across a package (mingw-qt5-qtquickcontrols) whose specfile isn't named .spec (in this case, mingw-qtquickcontrols.spec instead of mingw-qt5-qtquickcontrols.spec). As I understand it this is against the guildelines? (Shouldn't the build actually fail?) Can I just fix it by r