X-Spam-Check-By: sourceware.org
From: "Marshall Abrams" <mars AT gwu DOT edu>
To: <cygwin AT cygwin DOT com>
Subject: Suggestion: split vim support files into separate package
Date: Mon, 26 Jun 2006 11:07:57 -0400
Message-ID: <000301c69932$565feee0$080a17d1@yourbes5v9ftq9>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-Virus-Status: Clean
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

I want to suggest splitting vim support files (installed in
/usr/share/vim/vim<major-version>) into a separate package from the
binaries.  There are two versions of vim binaries in Cygwin, the no-X
version (vim), and the version with X GUI compiled in (gvim), but their
(major) versions are not always in sync (as recent posts on this list
illustrated).  The problem is that if you install the newer version in
the most obvious way, the support files for the older version get
deleted, and all of a sudden the older version which you're still using
doesn't function properly.  (For example, at the moment, installing the
latest no-X vim in Cygwin, at version 7.0, deletes the support files for
the latest version of gvim in Cygwin, at version 6.4.)

Of course there are various ways to work around this problem without too
much trouble, but why not just make the support files a separate package
with dependencies linking both versions of the binaries to it.  That
way, I assume, the older support files wouldn't go away if something
still depends on them.

Thanks.

Cygwin is great!


Marshall



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