I think the new 'installer' keyword is on every bug that needs it now.
http://bugs.winehq.org/buglist.cgi?product=Wine&keywords_type=allwords&a... shows 94 downloadable apps with keyword 'installer'. Here's a breakdown by component: 24 wine-misc 17 wine-ole 15 wine-msi 7 wine-binary 6 wine-net 4 wine-x11 4 wine-msxml 3 wine-programs 3 wine-kernel 2 wine-user 2 wine-setupapi 2 wine-richedit 1 wine-shdocvw 1 Wine-Rebar 1 wine-msvcrt 1 wine-gdi-(printing) 1 wine-directx-d3d
James is taking on the msi and setupapi ones, I think. Anyone else interested in plowing through these to see if we can resolve all the installer bugs before 1.0? - Dan
I wil be looking msxml.
On 9/26/06, Dan Kegel dank@kegel.com wrote:
I think the new 'installer' keyword is on every bug that needs it now.
http://bugs.winehq.org/buglist.cgi?product=Wine&keywords_type=allwords&a... shows 94 downloadable apps with keyword 'installer'. Here's a breakdown by component: 24 wine-misc 17 wine-ole 15 wine-msi 7 wine-binary 6 wine-net 4 wine-x11 4 wine-msxml 3 wine-programs 3 wine-kernel 2 wine-user 2 wine-setupapi 2 wine-richedit 1 wine-shdocvw 1 Wine-Rebar 1 wine-msvcrt 1 wine-gdi-(printing) 1 wine-directx-d3d
James is taking on the msi and setupapi ones, I think. Anyone else interested in plowing through these to see if we can resolve all the installer bugs before 1.0?
- Dan
On 9/26/06, Dan Kegel dank@kegel.com wrote:
I think the new 'installer' keyword is on every bug that needs it now.
http://bugs.winehq.org/buglist.cgi?product=Wine&keywords_type=allwords&a... shows 94 downloadable apps with keyword 'installer'. Here's a breakdown by component: 24 wine-misc 17 wine-ole 15 wine-msi 7 wine-binary 6 wine-net 4 wine-x11 4 wine-msxml 3 wine-programs 3 wine-kernel 2 wine-user 2 wine-setupapi 2 wine-richedit 1 wine-shdocvw 1 Wine-Rebar 1 wine-msvcrt 1 wine-gdi-(printing) 1 wine-directx-d3d
James is taking on the msi and setupapi ones, I think. Anyone else interested in plowing through these to see if we can resolve all the installer bugs before 1.0?
- Dan
Just a quick side.. We have a component for MSI, why not make ones for other installer types as well, such as (at the very least) InstallShield, and possibly WISE?
On 9/26/06, Tom Spear speeddymon@gmail.com wrote:
Just a quick side.. We have a component for MSI, why not make ones for other installer types as well, such as (at the very least) InstallShield, and possibly WISE?
MSI is a component of Windows and thus Wine. Installshield and WISE are proprietary products not affiliated with Windows.
On 9/26/06, James Hawkins truiken@gmail.com wrote:
On 9/26/06, Tom Spear speeddymon@gmail.com wrote:
Just a quick side.. We have a component for MSI, why not make ones for
other
installer types as well, such as (at the very least) InstallShield, and possibly WISE?
MSI is a component of Windows and thus Wine. Installshield and WISE are proprietary products not affiliated with Windows.
-- James Hawkins
IMHO, I disagree. On a base install of windows, under program files, there is an installshield driver, along with ikernel.exe. I may be wrong because it has been a while since I reinstalled windows, and so therefore it may be added when you run an installshield installer for the first time, but even still, directx is an "addon" to windows, but we have a component for it. Heck, even MSI is an "addon" to windows, in that it's listed under windows update and they release new versions of it. Granted directx and MSI are affiliated in that they are made by M$, but like I said, installshield requires a dll in order to enable to files to work, just as MSI and directx do.
On 9/26/06, Tom Spear speeddymon@gmail.com wrote:
On 9/26/06, James Hawkins truiken@gmail.com wrote:
On 9/26/06, Tom Spear speeddymon@gmail.com wrote:
Just a quick side.. We have a component for MSI, why not make ones for
other
installer types as well, such as (at the very least) InstallShield, and possibly WISE?
MSI is a component of Windows and thus Wine. Installshield and WISE are proprietary products not affiliated with Windows.
-- James Hawkins
IMHO, I disagree. On a base install of windows, under program files, there is an installshield driver, along with ikernel.exe. I may be wrong because it has been a while since I reinstalled windows, and so therefore it may be added when you run an installshield installer for the first time, but even still, directx is an "addon" to windows, but we have a component for it. Heck, even MSI is an "addon" to windows, in that it's listed under windows update and they release new versions of it. Granted directx and MSI are affiliated in that they are made by M$, but like I said, installshield requires a dll in order to enable to files to work, just as MSI and directx do.
Please do some research before you make statements like these. MSI and DirectX are produced and provided by Microsoft. InstallShield is produced and provided by Macrovision. InstallShield does require a dll in order to work: msi.dll. InstallShield is just a fancy wrapper around MSI, and, no, it's not a part of the Microsoft Windows Operating System in any way.
http://www.macrovision.com/products/flexnet_installshield/index.shtml
On 9/26/06, Dan Kegel dank@kegel.com wrote:
http://bugs.winehq.org/buglist.cgi?product=Wine&keywords_type=allwords&a... shows 94 downloadable apps with keyword 'installer'. Here's a breakdown by component: 24 wine-misc 17 wine-ole 15 wine-msi 7 wine-binary 6 wine-net 4 wine-x11 4 wine-msxml ...
Here's the breakdown as of Nov 3: 27 wine-misc 16 wine-ole 9 wine-msi 7 wine-net 5 wine-binary 4 wine-x11 4 wine-programs 4 wine-msxml ...
Here's the same breakdown, but for all apps, not just downloadable ones: 55 wine-misc 33 wine-binary 27 wine-ole 21 wine-msi 10 wine-net 9 wine-x11 8 wine-programs 5 wine-msxml 5 wine-kernel ...
Amazingly, MSI is no longer anywhere near the top of the list, thanks to James Hawkin's little Manhattan project. - Dan
-
Dan Kegel -
James Hawkins -
Tom Spear -
Vijay Kiran Kamuju