X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_YG X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Oleksandr Gavenko Subject: Re: [ANNOUNCEMENT] Updated: cygport-0.11.1-1 Date: Sun, 28 Oct 2012 15:28:34 +0200 Lines: 23 Message-ID: <87txtebu9p.fsf@gavenkoa.example.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 2012-10-11, Yaakov (Cygwin/X) wrote: > I have just released cygport-0.11.1 for the Cygwin distribution and the > Fedora Cygwin repository. New in this release: > > * Spec-style .cygport files > Filename constraints do not apply if NAME, VERSION, and RELEASE are > defined. That's great news (user feedback)! I just make my first .cygport file and surprised by policy on .cygport file names. I worry about maintaining clean VCS history of project and renaming files just for version update seems wrong practice in VCS. It is possible to workaround this issue be generating .cygport file during build process. But now I just place 'PACKAGE.cygport' into my source code tree. > These variables are intended to replace PN/PV/PR. > What does that mean? PN/PV/PR removed in future releases? -- Best regards! -- 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