Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <421E4F05.5020404@tlinx.org>
Date: Thu, 24 Feb 2005 14:02:45 -0800
From: Linda W <cygwin AT tlinx DOT org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: "'Cygwin List'" <cygwin AT cygwin DOT com>
Subject: Re: packg mngmnt model & other cygwin package releases...(where did they come from?)
References: <42091B63 DOT 1080908 AT tlinx DOT org> <20050208234325 DOT GA2944 AT efn DOT org> <420AAF5E DOT 1030506 AT tlinx DOT org> <420AB5EC DOT 1070904 AT familiehaase DOT de> <420BB627 DOT 7040905 AT tlinx DOT org> <20050210200410 DOT GA3728 AT efn DOT org> <420BEEB6 DOT 3070303 AT x-ray DOT at> <421CCF9A DOT 5010202 AT tlinx DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0502231348470 DOT 25676 AT slinky DOT cs DOT nyu DOT edu> <421CEAE3 DOT 3080401 AT tlinx DOT org> <20050224104137 DOT GE5708 AT efn DOT org>
In-Reply-To: <20050224104137.GE5708@efn.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes



Yitzchak Scott-Thoennes wrote:

> How is that not good publicity? There are a ton of cygwin binaries out
>
>there; all you need to find them is usually the package name, "cygwin",
>and google.  I know Gerrit, who maintains a lot of packages, also has
>a large number of things he's built and put out there with no intention
>to maintain them.  That's really sufficient; without someone responsible
>for maintaining them, they should only be available unofficially.
>
>  
>
Good point.  Unmaintained projects should be dropped when
they no longer work or are too outdated.  SGI had a "contrib"
CD (later became 2 CD's) that was totally composed of
unofficial, "volunteer effort" projects.  No official support
and provided on an "as is" basis.  They were only kept on the
CD(s) while they worked, or as long as they had someone
"sponsoring" a "util".  Mostly the CDs were composed of IRIX
ports of Gnu based utils...  It was just done as a convenience
for interested customers.  It was also only composed of
tools actually submitted for inclusion -- not "one of's" or
hacks that people didn't want included.

But all of this discussion is moot if there is no high level
interest in providing 3rd party links or a cygwin-contrib
section to setup.  Having all package dependancies specified
in the "setup" format _might_ be another obstacle to 3rd
party ports of existing rpm packages.  Rpm could be enhanced
to work with/around Window's file-copy semantics -- if by
no other method that using "sysinternals.com" "movefile"
utility which allows replacing of "in use" files (followed
by a reboot to finish the install just as setup does).

-linda


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