X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 	tests=AWL,BAYES_00,EXECUTABLE_URI,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4A96F466.1080204@cygwin.com>
References: <416096c60908271159i5e570a34wb61adbed5d6e34f5 AT mail DOT gmail DOT com> 	 <4A96F466 DOT 1080204 AT cygwin DOT com>
Date: Fri, 28 Aug 2009 19:55:18 +0100
Message-ID: <416096c60908281155v1b068feeoce674b2edab476eb@mail.gmail.com>
Subject: Re: Adding packages (was: mkfs.jffs2 support in CYGWIN)
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Larry Hall:
> Adding a link to <http://cygwin.com/setup.exe> shouldn't be allot of work
> and may help if the menu was properly named.

Good idea. I'll throw a name into the ring: "Cygwin package manager".

>=C2=A0Beyond that requires significant changes to 'setup.exe'

What would be needed beyond the packaging? I guess one problem is that
setup.exe couldn't update itself; could it rely on the "do it at next
reboot" solution instead?

> which would require some volunteer effort to make it happen.

Don't think I've got spare cycles to commit, unfortunately.

cgf:
> I've actually been trying to make setup.exe more usable from the command
> line so that it could be used as an update client like "yum" or "apt-get".

I think that's well worth doing, since many people do prefer that
approach. The big Linux distributions all seem to have ended up
supporting both the CLI and GUI approaches though, even if they
originally preferred one or the other.

Andy

--
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