Dear Scribus & Inkscape developers,
I love both your applications and would like to encourage my colleagues and students to use them. I notice that the OpenOffice team have now made their Windows version into an MSI package which will greatly ease the adoption of the package in University departments for example (which more commonly nowadays) often run WIndows Domains with centralized installation systems.
Any chance you guys would consider doing the same?
Kind regards,
tOnY
On Mon, May 15, 2006 at 04:03:42PM +0100, Antony J Mee wrote:
Dear Scribus & Inkscape developers,
I love both your applications and would like to encourage my colleagues and students to use them. I notice that the OpenOffice team have now made their Windows version into an MSI package which will greatly ease the adoption of the package in University departments for example (which more commonly nowadays) often run WIndows Domains with centralized installation systems.
Any chance you guys would consider doing the same?
We would certainly consider it if someone (such as yourself) were willing to help set up and maintain the packaging scripts for it. Interested?
Bryce
On Tuesday 16 May 2006 19:39, Bryce Harrington wrote:
On Mon, May 15, 2006 at 04:03:42PM +0100, Antony J Mee wrote:
Dear Scribus & Inkscape developers,
I love both your applications and would like to encourage my colleagues and students to use them. I notice that the OpenOffice team have now made their Windows version into an MSI package which will greatly ease the adoption of the package in University departments for example (which more commonly nowadays) often run WIndows Domains with centralized installation systems.
Any chance you guys would consider doing the same?
We would certainly consider it if someone (such as yourself) were willing to help set up and maintain the packaging scripts for it. Interested?
Bryce
I've added: http://bugs.scribus.net/view.php?id=3827
Good idea.
Peter
Antony,
thanks for you idea.
As this sound a reasonable good feature request I filed a RFE for you. So we won't loose that idea :-)
1490815 have a win32 installer as .msi package http://sourceforge.net/tracker/index.php?func=detail&aid=1490815&gro...
I think this is not possible for 0.44 but we can work on that later.
HTH,
Adib. --- PLinnell schrieb:
On Tuesday 16 May 2006 19:39, Bryce Harrington wrote:
On Mon, May 15, 2006 at 04:03:42PM +0100, Antony J Mee wrote:
Dear Scribus & Inkscape developers,
I love both your applications and would like to encourage my colleagues and students to use them. I notice that the OpenOffice team have now made their Windows version into an MSI package which will greatly ease the adoption of the package in University departments for example (which more commonly nowadays) often run WIndows Domains with centralized installation systems.
Any chance you guys would consider doing the same?
We would certainly consider it if someone (such as yourself) were willing to help set up and maintain the packaging scripts for it. Interested?
Bryce
I've added: http://bugs.scribus.net/view.php?id=3827
Good idea.
Peter
On Mon, 2006-05-15 at 16:03 +0100, Antony J Mee wrote:
Dear Scribus & Inkscape developers,
I love both your applications and would like to encourage my colleagues and students to use them. I notice that the OpenOffice team have now made their Windows version into an MSI package which will greatly ease the adoption of the package in University departments for example (which more commonly nowadays) often run WIndows Domains with centralized installation systems.
Any chance you guys would consider doing the same?
Kind regards,
tOnY
Hi tOnY, there is already a windows installer for Inkscape at least. I hope you can use that. It is NSIS-based, which is an open source installer. MSI is not an open source installer. Thus, you can see why we use NSIS, which many consider more effective...
You can find this installer (.nsi) on our http://sf.net/projects/inkscape/ files page.
Thanks, Jon
Hi tOnY, there is already a windows installer for Inkscape at least. I hope you can use that. It is NSIS-based, which is an open source installer. MSI is not an open source installer. Thus, you can see why we use NSIS, which many consider more effective...
You can find this installer (.nsi) on our http://sf.net/projects/inkscape/ files page.
There's an Open Source program to create MSI installers too: http://wix.sourceforge.net/
According to this slashdot story [1], Microsoft were the ones who released the source code.
It appears to only run on Windows, but I haven't spent any real time with it, I just came across it the other day.
[1] http://developers.slashdot.org/article.pl?sid=04/04/05/135241
Crossposting removed, make things exponentially more difficult to follow.
On Mon, 28 Aug 2006, Jon Phillips wrote:
Date: Mon, 28 Aug 2006 12:42:33 -0700 From: Jon Phillips <jon@...235...> To: Antony J Mee <A.J.Mee@...1277...> Cc: inkscape-devel@lists.sourceforge.net, scribus@...119... Subject: Re: [Inkscape-devel] MSI Packages
On Mon, 2006-05-15 at 16:03 +0100, Antony J Mee wrote:
Dear Scribus & Inkscape developers,
I love both your applications and would like to encourage my colleagues and students to use them. I notice that the OpenOffice team have now made their Windows version into an MSI package which will greatly ease the adoption of the package in University departments for example (which more commonly nowadays) often run WIndows Domains with centralized installation systems.
Any chance you guys would consider doing the same?
There are two standard responses to that: 1) Why? 2) Yes please! Do send patches ;)
I believe there are some features in MSI which make it easier to automate installs and rollout a program across a large organisation as you describe.
NSIS does provide various command line options for a silent install and it should be possible to automate things and perform an unattended install and it may even be possible to get that to work with the cetralised system you mention. Some installers do require a little adjustment to get silent install to work but so long as there are reasonable defaults set for everything it probably already works fine.
1) feeds into 2) since the more you know about the hows and whys the easier it is to help make it happen. Inkscape is great about accepting outside contributions so if you were willing to stick around look into the problem further you would get quite a bit of help making it happen and it is an opportunity for you to get involved. providing a really good report with details of the how to do it will help the next person and increase the chances of making things happen sooner.
Sincerely
Alan Horkan
Inkscape http://inkscape.org Abiword http://www.abisource.com Open Clip Art http://OpenClipArt.org
Alan's Diary http://advogato.org/person/AlanHorkan/
Jon Phillips wrote:
Hi tOnY, there is already a windows installer for Inkscape at least. I hope you can use that. It is NSIS-based, which is an open source installer. MSI is not an open source installer. Thus, you can see why we use NSIS, which many consider more effective...
I suspect the trouble is that MSI is automatically deployable and updatable across Active Directory networks, while other package formats are not.
It's possible to re-package apps into MSI format ones self if the original packager doesn't provide an MSI, but not everybody knows that or knows how to do it. It's also a lot more fuss.
Python is packaged as an MSI installer, as are a few other OSS apps. I'd be interested in knowing how they do it, actually, because Scribus could benefit from using the format eventually too.
This site has a whole bunch of info on Windows Installer and MSI:
http://www.appdeploy.com/techhomes/windowsinstaller.asp
Notably, WiX is listed under the "packaging tools" section, and it's OSS (CPL) .
Hope this is helpful.
-- Craig Ringer
participants (8)
-
Adib Taraben -
Alan Horkan -
Antony J Mee -
Bryce Harrington -
Craig Ringer -
Jon Phillips -
Michael Moore -
PLinnell