Jacek Caban jacek@codeweavers.com writes:
The following series of patches is a first step towards Wine Add-ons tool. These patches move Gecko installation to wineaddon.cpl. They do nothing about making install code generic nor provide any new GUI yet. They only place the code in the right place so that it can be improved further.
Is a separate control panel really the right place? It seems to me that it would be preferable if add-ons were treated more like normal packages, and in particular registered in the installed packages list. This would make it possible to manage them from the appwiz control panel, and from other tools that use install information like uninstaller.
On 12/6/10 1:15 PM, Alexandre Julliard wrote:
Jacek Cabanjacek@codeweavers.com writes:
The following series of patches is a first step towards Wine Add-ons tool. These patches move Gecko installation to wineaddon.cpl. They do nothing about making install code generic nor provide any new GUI yet. They only place the code in the right place so that it can be improved further.
Is a separate control panel really the right place? It seems to me that it would be preferable if add-ons were treated more like normal packages, and in particular registered in the installed packages list. This would make it possible to manage them from the appwiz control panel, and from other tools that use install information like uninstaller.
I must have misunderstood your plan then. Now I understand that we will have MSI file with self extracting archive for both Gecko and Mono that can be downloaded and/or installed by control panel applet. I agree that appwiz.cpl looks like a better place than a new applet for that.
Let's make it clear, what's the plan: The first step is moving the code to the right place (I will send patches moving it to appwiz.cpl). On the next Gecko release, we will change it to use MSI file and all goodies of more standard installation. Meantime we need some improvements. I know that André is looking at required 7zip improvements and Hans has looked at MSI file creation. I'm planning to add checksum checking and fix installation without z: drive mapping. Also some GUI changes and making the code more generic for Mono will be needed. It's up to Vincent when he's planning to add Mono package.
Jacek
On 06/12/2010 12:15, Jacek Caban wrote:
I must have misunderstood your plan then. Now I understand that we will have MSI file with self extracting archive for both Gecko and Mono that can be downloaded and/or installed by control panel applet. I agree that appwiz.cpl looks like a better place than a new applet for that.
Adding in an "optional components" tab to appwiz.cpl would seem to be the most sensible thing there, similar to that used in Windows. While you could have an entry in the Installed Programs list when they're installed, it would seem slightly perverse to include them in that list when they're not actually installed. To me, a separate tab would seem better.
On Mon, 2010-12-06 at 19:15 +0100, Jacek Caban wrote:
Let's make it clear, what's the plan: The first step is moving the code to the right place (I will send patches moving it to appwiz.cpl). On the next Gecko release, we will change it to use MSI file and all goodies of more standard installation. Meantime we need some improvements. I know that André is looking at required 7zip improvements and Hans has looked at MSI file creation. I'm
I wrote a simple tool that allows you to build an installer database from .idt files. Note that it's a winelib program, so using it will make Wine a build dependency of your project.
What improvements are needed for 7zip? It seems to work fine here, I can use both the Windows and the Linux version to create self-extracting archives for Windows.
On 12/6/10 8:13 PM, Hans Leidekker wrote:
On Mon, 2010-12-06 at 19:15 +0100, Jacek Caban wrote:
Let's make it clear, what's the plan: The first step is moving the code to the right place (I will send patches moving it to appwiz.cpl). On the next Gecko release, we will change it to use MSI file and all goodies of more standard installation. Meantime we need some improvements. I know that André is looking at required 7zip improvements and Hans has looked at MSI file creation. I'm
I wrote a simple tool that allows you to build an installer database from .idt files.
Sounds great, thanks.
Note that it's a winelib program, so using it will make Wine a build dependency of your project.
That's fine with me. I believe that distros will be able to cope with it as well.
What improvements are needed for 7zip? It seems to work fine here, I can use both the Windows and the Linux version to create self-extracting archives for Windows.
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
Jacek
What improvements are needed for 7zip? It seems to work fine here, I can use both the Windows and the Linux version to create self-extracting archives for Windows.
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
Check http://www.bugaco.com/7zip/MANUAL/switches/sfx.htm
SFX-header + config.txt + archive.7z = win.exe
I created such sfx-files on Linux to make the testbot run a bit more than the standard test-executables.
Regards,
Wolfram
On Mon, 2010-12-06 at 20:21 +0100, Jacek Caban wrote:
What improvements are needed for 7zip? It seems to work fine here, I can use both the Windows and the Linux version to create self-extracting archives for Windows.
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
$ rm -f wine_gecko-1.1.0.7z $ 7z a wine_gecko-1.1.0.7z wine_gecko-1.1.0.msi gecko/ $ cat 7zS.sfx wine_gecko-1.1.0.cfg wine_gecko-1.1.0.7z > wine_gecko-1.1.0.exe
where 7zS.sfx is the self-extractor and wine_gecko-1.1.0.cfg looks like this:
;!@Install@!UTF-8! Title="Wine Gecko 1.1.0" BeginPrompt="Do you want to install Wine Gecko 1.1.0?" ExecuteFile="wine_gecko-1.1.0.msi" ;!@InstallEnd@!
Am 06.12.2010 20:44, schrieb Hans Leidekker:
On Mon, 2010-12-06 at 20:21 +0100, Jacek Caban wrote:
What improvements are needed for 7zip? It seems to work fine here, I can use both the Windows and the Linux version to create self-extracting archives for Windows.
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
$ rm -f wine_gecko-1.1.0.7z $ 7z a wine_gecko-1.1.0.7z wine_gecko-1.1.0.msi gecko/ $ cat 7zS.sfx wine_gecko-1.1.0.cfg wine_gecko-1.1.0.7z > wine_gecko-1.1.0.exe
where 7zS.sfx is the self-extractor and wine_gecko-1.1.0.cfg looks like this:
;!@Install@!UTF-8! Title="Wine Gecko 1.1.0" BeginPrompt="Do you want to install Wine Gecko 1.1.0?" ExecuteFile="wine_gecko-1.1.0.msi" ;!@InstallEnd@!
So the only problem is to have the Windows sfx file in your Linux environment?
On Mon, 2010-12-06 at 20:49 +0100, André Hentschel wrote:
So the only problem is to have the Windows sfx file in your Linux environment?
Yeah, it would be nice to have a Linux package for it. The source appears to be in the public domain.
Am 06.12.2010 21:07, schrieb Hans Leidekker:
On Mon, 2010-12-06 at 20:49 +0100, André Hentschel wrote:
So the only problem is to have the Windows sfx file in your Linux environment?
Yeah, it would be nice to have a Linux package for it. The source appears to be in the public domain.
One plan was to send patches to p7zip to compile the sfx part twice(one time gcc, one time with mingw(-w64)) at buildtime, so that it is upstream. I am working on it, but i am also busy with other things.
Hans Leidekker hans@codeweavers.com writes:
On Mon, 2010-12-06 at 20:21 +0100, Jacek Caban wrote:
What improvements are needed for 7zip? It seems to work fine here, I can use both the Windows and the Linux version to create self-extracting archives for Windows.
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
$ rm -f wine_gecko-1.1.0.7z $ 7z a wine_gecko-1.1.0.7z wine_gecko-1.1.0.msi gecko/ $ cat 7zS.sfx wine_gecko-1.1.0.cfg wine_gecko-1.1.0.7z > wine_gecko-1.1.0.exe
where 7zS.sfx is the self-extractor and wine_gecko-1.1.0.cfg looks like this:
;!@Install@!UTF-8! Title="Wine Gecko 1.1.0" BeginPrompt="Do you want to install Wine Gecko 1.1.0?" ExecuteFile="wine_gecko-1.1.0.msi" ;!@InstallEnd@!
Of course it would be even nicer to pack everything inside the msi file, then we wouldn't need a self-extractor at all...
On Mon, 2010-12-06 at 23:14 +0100, Alexandre Julliard wrote:
where 7zS.sfx is the self-extractor and wine_gecko-1.1.0.cfg looks like this:
;!@Install@!UTF-8! Title="Wine Gecko 1.1.0" BeginPrompt="Do you want to install Wine Gecko 1.1.0?" ExecuteFile="wine_gecko-1.1.0.msi" ;!@InstallEnd@!
Of course it would be even nicer to pack everything inside the msi file, then we wouldn't need a self-extractor at all...
Yes, we considered that. It means we need to be able to create a cabinet file, which needs to be done with open source tools if we want distributions to include the packages. Wine itself seems to be about the only option there, but we don't support compression.
Hans Leidekker hans@codeweavers.com writes:
Yes, we considered that. It means we need to be able to create a cabinet file, which needs to be done with open source tools if we want distributions to include the packages. Wine itself seems to be about the only option there, but we don't support compression.
If we already need Wine to create the msi file then it shouldn't be an issue to use it to create the cabinet. Compression shouldn't be hard to add.
On 12/06/2010 08:21 PM, Jacek Caban wrote:
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
(I don't want to be rude but ...) RTFM
quoting `man 7z` from Ubuntu 10.04 :
EXAMPLE 2 7z a -sfx archive.exe dir1 add all files from directory "dir1" to SFX archive archive.exe (Remark : SFX archive MUST end with ".exe")
Am 06.12.2010 21:02, schrieb GOUJON Alexandre:
On 12/06/2010 08:21 PM, Jacek Caban wrote:
That's exactly the problem of creating Windows self-extracting archives on Linux. How do you do that?
(I don't want to be rude but ...) RTFM
quoting `man 7z` from Ubuntu 10.04 :
EXAMPLE 2 7z a -sfx archive.exe dir1 add all files from directory "dir1" to SFX archive archive.exe (Remark : SFX archive MUST end with ".exe")
So that will simply create a linux executable with an ".exe" extention. You should consider being more friendly, especially when you dont know what you are talking about.
On 12/06/2010 09:15 PM, André Hentschel wrote:
So that will simply create a linux executable with an ".exe" extention. You should consider being more friendly, especially when you dont know what you are talking about
Hey ! I said I didn't want to be rude and that's still true
RTFM is a kind of philosophy My teacher was always saying that and now, I'm proud of finding how something works just by reading the manual
Quoting the manual is relevant. If not, the manual should be improved.
That being said, Have a nice .. day/night guys (depends)
Am 06.12.2010 21:28, schrieb GOUJON Alexandre:
On 12/06/2010 09:15 PM, André Hentschel wrote:
So that will simply create a linux executable with an ".exe" extention. You should consider being more friendly, especially when you dont know what you are talking about
Hey ! I said I didn't want to be rude and that's still true
RTFM is a kind of philosophy My teacher was always saying that and now, I'm proud of finding how something works just by reading the manual
Quoting the manual is relevant. If not, the manual should be improved.
That being said, Have a nice .. day/night guys (depends)
Sry, still was reading it in a rude way, had a long day. so sry.
Hey ! I said I didn't want to be rude and that's still true
RTFM is a kind of philosophy
It's very hard to make RTFM not seem rude. Anything with the F word in it is, in my opinion, best left off this list. --Juan
On 12/6/10 1:41 PM, Juan Lang wrote:
Hey ! I said I didn't want to be rude and that's still true
RTFM is a kind of philosophy
It's very hard to make RTFM not seem rude. Anything with the F word in it is, in my opinion, best left off this list.
+1, Juan. Spell it out, Read the Fine Manual is what was intended, but could be misunderstood as a really rude comment.
I prefer directing folks to the document, be it a web page (Google is your Friend), manual or a manpage...
James McKenzie
-
Alexandre Julliard -
André Hentschel -
GOUJON Alexandre -
Hans Leidekker -
Jacek Caban -
James McKenzie -
Juan Lang -
Owen Rudge -
Wolfram Sang