From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Jul 16 15:50:04 2007
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
X-Original-To: freebsd-ports-bugs@FreeBSD.org
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
by hub.freebsd.org (Postfix) with ESMTP id 30E5116A406
for <freebsd-ports-bugs@FreeBSD.org>;
Mon, 16 Jul 2007 15:50:04 +0000 (UTC)
(envelope-from pfgshield-freebsd@yahoo.com)
Received: from web32702.mail.mud.yahoo.com (web32702.mail.mud.yahoo.com
[68.142.207.246])
by mx1.freebsd.org (Postfix) with SMTP id D52EE13C4EB
for <freebsd-ports-bugs@FreeBSD.org>;
Mon, 16 Jul 2007 15:50:03 +0000 (UTC)
(envelope-from pfgshield-freebsd@yahoo.com)
Received: (qmail 32950 invoked by uid 60001); 16 Jul 2007 15:50:02 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
h=Message-ID:X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
b=NN+VNulxZjgn7aq0i2YeD4cK3aPns5eAsNvBwibZAO3wmZ5ge+hiyF5BdHYw4pYtaIqU3LrUvShcijl5aUUbXdt/QoXVba7KMXTS4beGSXOPloz3oKS8XE2Mu8cLwg1FNmwVOCfTl0ICrQLb7hzKGdDF6uo1A+jqTnsY6BaoxkU=
;
Message-ID: <20070716155002.32948.qmail@web32702.mail.mud.yahoo.com>
X-YMail-OSG: MWjGbhgVM1m8gcc47Cq0sTCewjvWAjpyQdBYGsImsNf2x5B.76mXORo8AkF28PQwnSpk4LAI5WX2QdKOWZBXK7VpzfFlLv19fg2r
Received: from [200.118.59.147] by web32702.mail.mud.yahoo.com via HTTP;
Mon, 16 Jul 2007 17:50:02 CEST
Date: Mon, 16 Jul 2007 17:50:02 +0200 (CEST)
From: <pfgshield-freebsd@yahoo.com>
To: pav@FreeBSD.org
In-Reply-To: <1184600262.47371.2.camel@pav.hide.vol.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Mon, 16 Jul 2007 15:57:59 +0000
Cc: freebsd-ports-bugs@FreeBSD.org
Subject: Re: ports/114507: Cleanup x11-toolkits/xview
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pfgshield-freebsd@yahoo.com
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>,
<mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>,
<mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2007 15:50:04 -0000
--- Pav Lucistnik <pav@FreeBSD.org> ha scritto:
> > All the REINPLACING can be done in post-patch or pre-configure. I prefer
> > pre-configure to avoid the reinplacing getting confused with patches as
> > happened with this port.
>
> I prefer post-patch, so one can type `make patch' and observe the
> results of replacing, without need to run configure script.
I used to think this but then if the maintainer edits those files the
reinplacing will get into the patches (some files are patched and reinplaced).
This was indeed what happened and thats why I had to clean up the double
reinplacing.
> Can this be changed back?
That said it's a matter of pure taste. Feel free to change it back to
post-patch.
Pedro.
___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html