public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: AW: [bulk] - Re: Reduce noise in dependency declaration during uninstall in setup.exe
Date: Thu, 23 Jan 2014 16:41:00 -0000	[thread overview]
Message-ID: <52E1462F.30505@cygwin.com> (raw)
In-Reply-To: <8CCC8F85C5F2784387A32FAD835FB4E60EC1EC706D@server03.company.internal>

On 1/23/2014 10:40 AM, DEWI - N. Zacharias wrote:

<snip>

>
> [...]
>
>> One solution to this would be to reimplement it as two separate parts -
>> a non-Cygwin envelope (which could even be installed as an msi) and a
>> Cygwin-based package maintainer.  The Cygwin-based part would be a
>> completely separate Cygwin installation, with its own cygwin1.dll, and a
>> minimal set of utilities, and would not interfere with the main
>> installation.
>> The non-cygwin wrapper would simply install/update this mini-Cygwin
>> system and invoke the Cygwin-based package maintainer.
>
> I second this idea.
>
>> The package maintainer would be based on the existing setup.exe,
>
> I think this is not that good. If you rewrite the tool you should throw
> away ballast and use the chance to include new helpful things like a clean
> interface to an installation config file which allows cloning of existent
> installations.

Unless there's someone reading this thread that's actually going to jump
in and start working on setup-next-generation, I'd like to ask others that
are considering adding to this thread to not do so.  Talking about what
would be great as a next-generation version of setup has been done plenty
in the past and it's quite likely that a continuation of this thread along
this line will rehash what has already been said.  What's missing isn't
ideas on how to make a better setup facility.  What's missing are the
brave and capable souls to do it.  If this describes you, I'd recommend
checking the archives for previous discussions on this subject and
then proposing a plan based on those discussions.  Best to do that on the
cygwin-apps list though.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-01-23 16:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  0:06 Warren Young
2014-01-22  0:44 ` Warren Young
2014-01-22  1:02   ` Larry Hall (Cygwin)
2014-01-22  6:02     ` Christopher Faylor
2014-01-22 15:04       ` Corinna Vinschen
2014-01-23 16:35         ` Andrey Repin
2014-01-23 17:01         ` Thrall, Bryan
2014-01-23 17:20           ` Andrey Repin
2014-01-23 17:37             ` Thrall, Bryan
2014-01-23 17:47           ` Corinna Vinschen
2014-01-22 21:04       ` Warren Young
2014-01-23  1:13         ` Christopher Faylor
2014-01-23 14:36           ` Warren Young
2014-01-23 15:18             ` Cliff Hones
2014-01-23 15:40               ` AW: [bulk] - " DEWI - N. Zacharias
2014-01-23 16:41                 ` Larry Hall (Cygwin) [this message]
2014-01-23 16:32               ` Warren Young
2014-01-23 17:20               ` Andrey Repin
2014-01-23 17:58 ` Achim Gratz
2014-01-23 20:11   ` Warren Young

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=52E1462F.30505@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.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).