From owner-freebsd-ports@FreeBSD.ORG Wed Jun 2 13:59:31 2004 Return-Path: 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 45E7316A4CE; Wed, 2 Jun 2004 13:59:31 -0700 (PDT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC00043D1D; Wed, 2 Jun 2004 13:59:30 -0700 (PDT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) i52KxTfQ073674; Wed, 2 Jun 2004 22:59:29 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id i52KxOsr073673; Wed, 2 Jun 2004 22:59:24 +0200 (CEST) (envelope-from marius) Date: Wed, 2 Jun 2004 22:59:24 +0200 From: Marius Strobl To: FreeBSD ports , Alexander Leidinger , trevor@FreeBSD.org, Oliver Eikemeier Message-ID: <20040602225924.Z251@newtrinity.zeist.de> References: <200406021944.i52JikWH025330@8ball.rtp.freebsd.org> <20040602222032.Y251@newtrinity.zeist.de> <20040602203933.GA83720@droso.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040602203933.GA83720@droso.net>; from erwin@FreeBSD.org on Wed, Jun 02, 2004 at 10:39:33PM +0200 X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.25.0.60; VDF 6.25.0.82 (host: newtrinity.zeist.de) Subject: Re: Ports with a broken PKGORIGIN: chinese/cdrtools X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 20:59:31 -0000 On Wed, Jun 02, 2004 at 10:39:33PM +0200, Erwin Lansing wrote: > On Wed, Jun 02, 2004 at 10:20:32PM +0200, Marius Strobl wrote: > > > > Ok, I missed that chinese/cdrtools got hooked up as a slave-port > > to sysutils/cdrtools. But chinese/cdrtools does conflict with the > > files installed by sysutils/cdrtools and moreover really only > > patches mkisofs. > > Maybe I'm mistaken, but why should a slave port not be able to conflict > with it's master? I think that most slaves actually do, so just a > question of setting the right CONFLICTS? Certainly it's ok for a slave-port to conflict with its master if both set CONFLICTS appropriately. But: a) chinese/cdrtools and sysutils/cdrtools don't set CONFLICTS for each other. b) Until today sysutils/cdrtools didn't install mkisofs and neither did chinese/cdrtools but chinese/cdrtools only patches the mkisofs sources. So you had two ports installing exacly the same stuff. So this isn't an issue with sysutils/cdrtools as the master but chinese/cdrtools doesn't/didn't make sense as a slave. As I currently see it the best would be to turn chinese/cdrtools into chinese/mkisofs-2byte (not sure about the name) and maybe move chinese/mkisofs to chinese/mkisofs-big5. Does this make sense? > > > Could someone please disconnect chinese/cdrtools from the build > > until this is resolved? > > > Done. And don't worry, I'll keep nagging you until it's hooked up again > :-) Thanks!