From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Nov 17 16:46:59 2005 Return-Path: X-Original-To: freebsd-ports-bugs@FreeBSD.org Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 202DC16A421 for ; Thu, 17 Nov 2005 16:46:59 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (hood.oook.cz [195.250.137.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC4743DB9 for ; Thu, 17 Nov 2005 16:46:26 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from ikaros.oook.cz (localhost [127.0.0.1]) by hood.oook.cz (8.13.4/8.13.4) with ESMTP id jAHGkPAn059115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 17 Nov 2005 17:46:25 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by ikaros.oook.cz (8.13.4/8.13.4/Submit) id jAHGkPYS059114 for freebsd-ports-bugs@freebsd.org; Thu, 17 Nov 2005 17:46:25 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: ikaros.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: freebsd-ports-bugs@FreeBSD.org In-Reply-To: <200511170832.06601.ringworm01@gmail.com> References: <200511171540.jAHFeJSL017500@freefall.freebsd.org> <200511170807.46482.ringworm01@gmail.com> <1132244794.79514.28.camel@localhost> <200511170832.06601.ringworm01@gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 17 Nov 2005 17:46:25 +0100 Message-Id: <1132245985.79514.32.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Cc: Subject: Re: ports/89164: [PATCH] /var/db/pkg/{portname}/+CONTENTS files sometimes contain wrong data X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:46:59 -0000 > > > > Could you send the standalone bsd.port.mk patch to this PR? > > > > > > Sorry, should have said where it was, gets put > > > into /usr/local/share/portmanager but I'll attach the patch to this > > > message anyways. > > > > So this incorporates your portmanager into bsd.port.mk? I'm afraid we > > can't possibly include this in the official ports tree without making > > portmanager part of base system, do we? > > > > What kind of feedback you're expecting from us, then? > > Most important is that you recognize there is a problem with > how +CONTENTS files are generated. Yes, there is a long standing problem and we're aware of it. Sadly, no workable solution was submitted so far (at least I haven't found any PR filed against it). > Wether or not you all choose to make portmanager as a part > of the base system is up to you all, I really just wanted to let > you know that when portmanager is installed in a user system > I'd like it to make the adjustment to bsd.ports.mk. If portmanager > is removed I'll make sure it smoothly returns bsd.ports.mk > to a usefull state as part of the deinstall process. You're free to do whatever you want in your software. Just note that you have to patch bsd.ports.mk every time user cvsuped the tree, not only on portmanager install/deinstall. -- Pav Lucistnik On real UNIX, /usr/bin/more prints -More-.