From owner-freebsd-ports@FreeBSD.ORG Mon May 15 21:01:23 2006 Return-Path: X-Original-To: ports@freebsd.org 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 2393716B54A; Mon, 15 May 2006 21:01:23 +0000 (UTC) (envelope-from fernan@iib.unsam.edu.ar) Received: from smtp.unsam.edu.ar (smtp.unsam.edu.ar [170.210.48.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC62D43D55; Mon, 15 May 2006 21:01:15 +0000 (GMT) (envelope-from fernan@iib.unsam.edu.ar) Received: from omega.iib.unsam.edu.ar (omega.iib.unsam.edu.ar [192.168.10.14]) by smtp.unsam.edu.ar (8.12.6/8.12.6) with ESMTP id k4FL33oh092507; Mon, 15 May 2006 18:03:03 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: from omega.iib.unsam.edu.ar (localhost [127.0.0.1]) by omega.iib.unsam.edu.ar (8.13.6/8.13.6) with ESMTP id k4FL0vYN005634; Mon, 15 May 2006 18:00:57 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: (from fernan@localhost) by omega.iib.unsam.edu.ar (8.13.6/8.13.3/Submit) id k4FL0uIi005629; Mon, 15 May 2006 18:00:56 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) X-Authentication-Warning: omega.iib.unsam.edu.ar: fernan set sender to fernan@iib.unsam.edu.ar using -f Date: Mon, 15 May 2006 18:00:56 -0300 From: Fernan Aguero To: Daniel Eischen Message-ID: <20060515210056.GL38981@iib.unsam.edu.ar> Mail-Followup-To: Daniel Eischen , FreeBSD Ports , xmcd@amb.org References: <20060515190027.GI38981@iib.unsam.edu.ar> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.11 Cc: FreeBSD Ports , xmcd@amb.org Subject: Re: cddb working in xmcd? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 21:01:24 -0000 +----[ Daniel Eischen (15.May.2006 16:47): | | >Maybe we can add an optional WITH_FREEDB knob to the port? | | I've been asked to do that before in the FreeBSD port, and my | answer is still the same. I don't want to change the author's | work except for what it takes to integrate with FreeBSD and | our ports tree. | +----] Sounds reasonable ... I can live with that and keep my patch-fcddb.h for as long as I need it (cvsup won't delete it). However, as mentioned by the Xmcd admin in a private reply to my original message, maybe the problem was that I'm using a xmcd compiled to use CDDB1 "classic" CDDB protocol which connects to Gracenote's CDDB1-to-CDDB2 gateway. It might be that this is the cause of the problems. I started researching this issue in complete naiveness ... thus I was being completely naive when I suggested the WITH_FREEDB option. Now, after digging a while in google, it seems like this lack of support for other cddb1 databases is forced on developers by gracenote (you have to agree to their license terms if you want to include support for cddb2, which includes the prohibition to use any other CD info database). So maybe this is the road followed by xmcd? It is curious that the support for entering CDDB URLs freely into a text configuration file (common.cfg) was removed in recent xmcd versions, while it was there previously. After reading the changelog for xmcd, it seems likely that this was brought about as part of the 3.0 release which introduced CDDB2 support. Taken from: http://www.ibiblio.org/tkan/xmcd/changes.txt Fro the 3.0 patchlevel 0 notes: - Some parameters have been removed and new parameters added to the common.cfg file. These reflect the change to CDDBČ and other new or different capabilities in this release. And so I got to understand why xmcd hardcodes cddb.com servers in fcddb.h, why configuration of cddb servers cannot be done in the app, etc. These were things that striked me as odd given the maturity and the otherwise ease of use I've found in xmcd (I've been using it for just two days!) So now that I know this, perhaps the best alternative is to keep the port building by default without CDDB2 support (as it is now). In this case I would suggest, to add a patch that fixes submission of CDDB data in classic CDDB1 mode. http://www.ibiblio.org/tkan/xmcd/xmcd332-cddb1patch.gz This will provide everyone with a xmcd that is fully CDDB1 functional. Even if you don't want to include the patch I suggested in the stock xmcd port, users can still apply it or edit the fcddb.h file manually if they so wish. Fernan