For the builddep commands in http://wiki.winehq.org/Fedora to work as intended, there needs to be a repository containing the source rpms. The binary rpms do NOT provide the _build_ dependency information needed for the builddep commands to do their job.
Otherwise, the instructions need to be redone, as the builddep commands are not really doing anything useful as things stand.
Jeff
2016-01-02 15:49 GMT+08:00 Jeffrey Smith whydoubt@gmail.com:
For the builddep commands in http://wiki.winehq.org/Fedora to work as intended, there needs to be a repository containing the source rpms. The binary rpms do NOT provide the _build_ dependency information needed for the builddep commands to do their job.
Otherwise, the instructions need to be redone, as the builddep commands are not really doing anything useful as things stand.
Hi Jeffery, Thank you for caring it.
I added builddep commands before we provide official builds on https://dl.winehq.org/wine-builds/ And I haven't tested it if the repo is added.
Should we add the build dependency information in src.rpm ?
On Sat, 2 Jan 2016 01:49:40 -0600 Jeffrey Smith whydoubt@gmail.com wrote:
For the builddep commands in http://wiki.winehq.org/Fedora to work as intended, there needs to be a repository containing the source rpms. The binary rpms do NOT provide the _build_ dependency information needed for the builddep commands to do their job.
Otherwise, the instructions need to be redone, as the builddep commands are not really doing anything useful as things stand.
I assume you mean the line about using dnf builddep to install the build dependencies on Fedora 22 and later. I've removed that. I've left the command from Zhenbo Li, because AFAIK it should install everything listed, and all those things are needed, but I'm not sure the list includes everything needed. The original wording on that page suggested that it was needed in addition to running dnf builddep. Hence the "This section is incomplete" note I've also added; someone who uses Fedora will need to expand that section, or tell me what to add.
Is there any point in keeping the Old Fedora section on that page?
Fedora 21 was EOL'd a month ago, and I don't believe the yum-builddep commands work without the source rpms either. So the Old Fedora section probably could go away.
If a patch of mine to the dnf project is approved, and if a source repo is added along-side the winehq binary repo, then perhaps the dnf builddep command can eventually replace that lengthy dnf install command.
One more question: where is the Fedora spec file used for creating the winehq binary packages. That should be available somewhere, but I haven't found it.
On Sat, Jan 2, 2016 at 9:36 AM, Rosanne DiMesio dimesio@earthlink.net wrote:
On Sat, 2 Jan 2016 01:49:40 -0600 Jeffrey Smith whydoubt@gmail.com wrote:
For the builddep commands in http://wiki.winehq.org/Fedora to work as intended, there needs to be a repository containing the source rpms. The binary rpms do NOT provide the _build_ dependency information needed for the builddep commands to do their job.
Otherwise, the instructions need to be redone, as the builddep commands
are
not really doing anything useful as things stand.
I assume you mean the line about using dnf builddep to install the build dependencies on Fedora 22 and later. I've removed that. I've left the command from Zhenbo Li, because AFAIK it should install everything listed, and all those things are needed, but I'm not sure the list includes everything needed. The original wording on that page suggested that it was needed in addition to running dnf builddep. Hence the "This section is incomplete" note I've also added; someone who uses Fedora will need to expand that section, or tell me what to add.
Is there any point in keeping the Old Fedora section on that page?
-- Rosanne DiMesio dimesio@earthlink.net
Am 02.01.2016 um 19:08 schrieb Jeffrey Smith:
One more question: where is the Fedora spec file used for creating the winehq binary packages. That should be available somewhere, but I haven't found it.
You can find all packaging files at: https://github.com/wine-compholio/wine-packaging (we should change the name of the github team at some point)
If you want to generate the build files for all targets: ./generate.py --out some_dir
If you also want the script to download all required files (i.e. the wine source code), you can use: ./generate.py --out some_dir --boot
Just ignore the created boot.sh file. This file is executed in our build VMs and contains the instructions on how to build packages on this system. For Fedora it basically just tells the VM to install the build dependencies and build the spec file.
In case you only want to get the files for fedora, you can use: ./generate.py --out some_dir --skip-name (--boot) \ fedora-any-development
The --skip-name parameter prevents the script from creating subdirectories for each distribution.
Regards, Michael
-
Jeffrey Smith -
Michael Müller -
Rosanne DiMesio -
Zhenbo Li