From rock-devel-bounces@rocklinux.org Fri Jan 28 21:52:48 2005 Received: from phoenix.clifford.at (localhost.localnet [127.0.0.1]) by phoenix.clifford.at (8.12.10/8.12.10) with ESMTP id j0SKk22c023070; Fri, 28 Jan 2005 21:46:19 +0100 Received: from smtp07.web.de (smtp07.web.de [217.72.192.225]) by phoenix.clifford.at (8.12.10/8.12.10) with ESMTP id j0SKk02b023064 for ; Fri, 28 Jan 2005 21:46:00 +0100 Received: from [217.232.219.253] (helo=smtp.anvame.net) by smtp07.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.103 #192) id 1Cuczq-0002gV-00 for rock-devel@rocklinux.org; Fri, 28 Jan 2005 21:45:38 +0100 Received: from andreas by smtp.anvame.net with local (Exim 4.43) id 1Cuczp-0000Yo-6I for rock-devel@rocklinux.org; Fri, 28 Jan 2005 21:45:37 +0100 Date: Fri, 28 Jan 2005 21:45:37 +0100 From: "Andreas V. Meier" To: ROCK Development Mailing List Message-ID: <20050128204537.GG5686@waterworld.anvame.net> Mime-Version: 1.0 User-Agent: Mutt/1.4.1i X-Sender: avmeier@web.de Subject: [rock-devel] patchlevel X-BeenThere: rock-devel@rocklinux.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: ROCK Development Mailing List List-Id: ROCK Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0040525659==" Sender: rock-devel-bounces@rocklinux.org Errors-To: rock-devel-bounces@rocklinux.org --===============0040525659== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="D6IIOQQv2Iwyp54J" Content-Disposition: inline --D6IIOQQv2Iwyp54J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi *, another thing I would like to clarify is the use of the patchlevel or also called extra version field. IMHO it should be increasend in every case where the resulting package changes, be it an added patch, an added option or something like that. Updates to the package should always reset the patchlevel to 0. I see a few patches in submaster that don't follow that scheme, so I want to clarify the usage of that. I may be wrong, if so, please correct me. But the patchlevel is mainly used by people who are looking for an updated package. if they see the same filename, they expect the same content. Otherwise we should stop cursing those projects that repeatedly change the contents of their files without changing the version number.=20 Ciao Andreas --D6IIOQQv2Iwyp54J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFB+qRx2A9/vRi9PS4RAkrkAJ0QWECy/1xGEduiTgiMcFSqQ7NHjACfY2yw sIaye8O5NW1Q3sJDUzOfFo8= =nwjI -----END PGP SIGNATURE----- --D6IIOQQv2Iwyp54J-- --===============0040525659== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rock-devel mailing list rock-devel@rocklinux.org https://www.rocklinux.net/mailman/listinfo/rock-devel --===============0040525659==--