public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Cc: Monica Parker <monicaparker@cymertek.com>
Subject: Re: msi installer file?
Date: Wed, 9 Mar 2022 22:22:48 +0000	[thread overview]
Message-ID: <20220309222248.hgmqihgvysjtd74h@lucy.dinwoodie.org> (raw)
In-Reply-To: <CAL9vbys48dQXrtZDc8Zvqu1=JGuNoKmGiuGyK7a7KkZXSO4dzQ@mail.gmail.com>

On Wed, Mar 09, 2022 at 02:27:01PM -0500, Monica Parker wrote:
> Hi,
> I just want to know if there is an MSI installer file? If not, can one be
> created? Im trying to create a package for SCCM and it wont accept exe
> files.

There isn't, and I don't think it's likely that anyone here will create
one; I'm not very familiar with the requirements for MSI installers, but
I very strongly expect that converting Cygwin's current installer to
work as an MSI installer would be *a lot* of work, if it's possible at
all.

In particular, the Cygwin installer is really a tool for selecting from
over 10,000 separate packages, calculating the potentially-complex
dependencies between them, then downloading and installing each
individual requested component.

If you want to provide a Cygwin installer in an environment where MSI
packages are acceptable but users can't run any executables, I expect
your best bet might be to decide what set of packages you want to
provide, install those using the regular Cygwin installer, then bundle
up the resultant installation directory into an MSI yourself.  That's
not going to be trivial to get working reliably, and obviously users
will lose the ability to select their own packages or get updates
until/unless you repackage them, but it's the best idea I can think of.

(I'm not familiar with SCCM, but given just how many Windows installers
come as executables, I'd have expected any management system that wanted
to intstall anything more than a very tightly controlled set of
applications would need to handle .exe installers.  I know Microsoft are
keen to get more people offering applications through their storefront,
but they're also actively working on winget, which can and does handle
.exe installers...)

  parent reply	other threads:[~2022-03-09 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 19:27 Monica Parker
2022-03-09 19:32 ` Bill Stewart
2022-03-09 22:22 ` Adam Dinwoodie [this message]
2022-03-10  7:58 ` Antonio Petrelli
2022-03-10 10:04 ` rappard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220309222248.hgmqihgvysjtd74h@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin@cygwin.com \
    --cc=monicaparker@cymertek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).