Mailinglist Archive: opensuse-buildservice (88 mails)

< Previous Next >
Re: [opensuse-buildservice] EXE package format
  • From: Martin Koegler <martin.koegler@xxxxxxxxx>
  • Date: Tue, 25 Feb 2014 20:03:36 +0100
  • Message-id: <20140225190336.GA25126@mail.zuhause>
On Tue, Feb 25, 2014 at 07:41:00AM +0100, Adrian Schröter wrote:
On Dienstag, 25. Februar 2014, 04:09:05 wrote Jan Engelhardt:

At the end of the
https://en.opensuse.org/openSUSE:Build_Service_comparison wiki page is
a comparison of build infrastructures, and in the column "package
format", OBS is said to support - even if only experimentally - the
"exe" package format.

A grep for zip\b or exe\b in the files of build.rpm does not yield any
hint towards zip/exe generation, so where exactly may I find it? Having
the actual program .exe in an .rpm is not too useful for Windows users???
(but using mingw works really well otherwise!).

there is no such support in build, but one could add it via a hook using

/usr/lib/build/checks/$script

mechanism. This could extract the exe file and store it as seperate build
result in OTHER directory.

I have done this via spec:
https://build.opensuse.org/package/show/home:e9925248:mingw/mingw64-grandorgue

A generic script is not able to find the useable parts. It is only useful to
extract
a installer, which also includes the DLLs and other resources.

Currently, the exe-Files from OTHER are only available to registered OBS users.
A drawback is, that without login, there is no indication, that you can
download it after login.

The publisher would need a few more lines to support publishing of these
.exe lines, but that can get added fast.

+1 for publishing such EXE to download.opensuse.org

Zypper for Mingw would probably be the best solution.

Otherwise, OBS should probably integrate something like that:
http://lists.opensuse.org/opensuse-mingw/2014-02/msg00000.html

Regards,
Martin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups