Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 21 Feb 2001 21:08:27 -0500 From: Christopher Faylor To: Corinna Vinschen Subject: Re: [ANNOUNCEMENT]: Important change to symbolic link functionality Message-ID: <20010221210827.C7576@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Corinna Vinschen References: <20010221232921.X908@cygbert.vinschen.de> <3A946EF1.3417756C@etr-usa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A946EF1.3417756C@etr-usa.com>; from warren@etr-usa.com on Wed, Feb 21, 2001 at 06:44:17PM -0700 On Wed, Feb 21, 2001 at 06:44:17PM -0700, Warren Young wrote: >Corinna Vinschen wrote: >>The next version of the Cygwin DLL will have the version number 1.3.0 >>to make unmistakeably clear that there are changes which breaks >>compatibility with older versions in a more serious manner than before. > >Will the DLL name change to, say, cygwin2.dll? There is a serious >problem with the DLL name "cygwin1.dll" going clear back to the beta 18 >days, IIRC. Whenever binary compatibility gets broken, the DLL file >name should change. There is no "binary compatibility change". Cygwin still recognizes the old symlinks. It just doesn't create them. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple