Suggestion: split vim support files into separate package

[Christopher Faylor]

On Mon, Jun 26, 2006 at 11:47:08AM -0400, Igor Peshansky wrote:
>An alternative is to introduce explicitly versioned dependencies (i.e.,
>where the version becomes part of the package name).  This is already done
>for shared library packages -- whenever a new version gets released, a
>compatibility package with the old version gets split off.  The problem is
>that this is quite a bit of effort, <http://cygwin.com/acronyms/#SHTDI>,
>and the vim/gvim maintainers are (appropriately) not willing to invest
>that much effort.  While it's necessary for shared libraries (since you
>never know who will be needing the old DLL version), I don't think this
>would be too useful for two sister packages like vim and gvim.

OTOH, if we had *rpm* for a package handler, this kind of thing would be
detected and there would be warnings and everything!

cgf

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