From owner-freebsd-ports Mon Mar 24 11:36:34 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C38C37B401 for ; Mon, 24 Mar 2003 11:36:32 -0800 (PST) Received: from remotely.cool.de (remotely.cool.de [212.169.188.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3477043F75 for ; Mon, 24 Mar 2003 11:36:30 -0800 (PST) (envelope-from jan-peter.koopmann@seceidos.de) Received: from firewall.seceidos.de ([62.138.174.141] helo=mail.seceidos.de) by remotely.cool.de with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.10) id 18xXkm-000GiE-00 for ports@FreeBSD.org; Mon, 24 Mar 2003 20:37:04 +0100 Received: from message.intern.akctech.de ([192.168.200.250]) by mail.seceidos.de with esmtp (Exim 4.12) id 18xXk6-000CBu-00; Mon, 24 Mar 2003 20:36:22 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: MailScanner port update question Disposition-Notification-To: "Jan-Peter Koopmann" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Mon, 24 Mar 2003 20:36:22 +0100 Message-ID: <4E7026FF8A422749B1553FE508E0068007F011@message.intern.akctech.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MailScanner port update question Thread-Index: AcLyOjx1ECp1ixKlSAKdu+qq8GMXzAAAZ6ZA From: "Jan-Peter Koopmann" To: "Erwin Lansing" Cc: X-MailScanner: Found to be clean X-MailScanner-SpamCheck: X-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,QUOTED_EMAIL_TEXT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi Erwin, > The easiest would be to write a follow-up to the original PR=20 > with the new version. You probably want to include a link to=20 > the new tarball/shar as it's rather large. Otherwise, file a=20 > new PR and ask for the original to be closed. Thanks for the quick answer! In the first version I had to supply the man pages via patches. The man pages will be part of the download in the next version therefore the port will be a lot(!) smaller. Maybe I will really send in a completely new version and ask the guys to close the first request. Might be the easiest solution for all this time.=20 Once this is in the ports tree how do I update the port? Via send-pr and new "bug reports" flagged as change-requests? And what is the best solution then? Diffs or complete new shar-archives? Sorry to get on all of your nerves but this is the first port I am contributing and I have not found any (clever) instructions on this in the porters handbook.=20 This way of updating a port appears a bit complicated to me but I suppose this kind of discussion has been here some times so I will better not start it again. :-) What is your experience? How quickly are change-requests adopted into the ports-tree in general? Regards, JP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message