From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 1 22:33:12 2008 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B633716A41A; Tue, 1 Jan 2008 22:33:12 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmmtao103.cox.net (eastrmmtao103.cox.net [68.230.240.9]) by mx1.freebsd.org (Postfix) with ESMTP id 535FE13C469; Tue, 1 Jan 2008 22:33:12 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080101223312.BRUK24467.eastrmmtao103.cox.net@eastrmimpo03.cox.net>; Tue, 1 Jan 2008 17:33:12 -0500 Received: from mezz.mezzweb.com ([24.255.149.218]) by eastrmimpo03.cox.net with bizsmtp id XyMZ1Y0064iy4EG0000000; Tue, 01 Jan 2008 17:21:34 -0500 Date: Tue, 01 Jan 2008 16:33:57 -0600 To: "Chuck Robey" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <1199159561.6089.2.camel@fermi> <477AA272.3080501@chuckr.org> <200801011627.46473.chuckr@chuckr.org> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <200801011627.46473.chuckr@chuckr.org> User-Agent: Opera Mail/9.25 (Linux) Cc: gnome@freebsd.org, Luis Medinas , Joe Marcus Clarke Subject: Re: Brasero on FreeBSD X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jan 2008 22:33:12 -0000 On Tue, 01 Jan 2008 15:27:46 -0600, Chuck Robey wrot= e: > On Tuesday 01 January 2008 04:13:14 pm Jeremy Messenger wrote: >> On Tue, 01 Jan 2008 14:28:34 -0600, Chuck Robey = >> wrote: >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> > >> > Joe Marcus Clarke wrote: >> >> On Tue, 2008-01-01 at 03:52 +0000, Luis Medinas wrote: >> >>> Hi >> >>> >> >>> As a co-maintainer of Brasero i'm tempted to ask why FreeBSD hasn= 't >> >>> brasero 0.7.0 on the ports tree. None of us are using FreeBSD sad= ly >> >>> but we can work together to make it work better for FreeBSD if it= >> >>> isn't working atm. Please bump brasero. >> >> >> >> First, this is very encouraging. I love it when maintainers make = an >> >> effort to help port their application to another platform. Thank = = >> you. >> >> >> >> Now for the bad news. We have quite a few users that want to use >> >> brasero on FreeBSD, but we haven't had anyone step up to fix the >> >> problems. Admittedly, I offered to look into this a while ago, bu= t >> >> fell behind with non-FreeBSD work, and the FreeBSD hal port update= . >> >> Here's were we stand with brasero now: >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/115240 : This l= ooks >> >> like a problem with brasero overriding PATH for a Linux-centric >> >> environment. mkisofs is found in /usr/local/bin on FreeBSD. >> >> Admittedly, I have not looked into the brasero code to determine i= f >> >> this is the case, or if this problem is still relevant in 0.7.0. >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/117364 : This i= s a >> >> bit nastier. FreeBSD's cdrecord only supports the legacy >> >> bus,target,lun notation. Our HAL exports this address via the >> >> block.freebsd.cam_path property, and I hacked nautilus-cd-burner t= o >> >> support this property on FreeBSD. >> >> >> >> If you have suggestions on these problems, I would be happy to get= >> >> brasero up to 0.7.0 and working properly on FreeBSD. >> > >> > I didn't know what brasero was, so I wewnt to their website. I fou= nd >> > that >> > the version number for their stable release is 0.5.2, while I see t= he >> > ports >> >> Which website? In the http://www.gnome.org/projects/brasero/ shows th= at >> 0.7.x is stable release. > > Hmm, I see. I was getting ready to jump on you for not reading = > carefully, > but when I looked at the home page of the page I *had* been using, I s= aw = > a > totally differnt answer. I'll give you both of them and maybe you'll = see > what I mean: > > http://www.gnome.org/projects/brasero/screenshots.html > (look at the download section on the right hand side, where it specifi= es > 0.5.2 as the stable one) > > http://www.gnome.org/projects/brasero/index.html > (this is the home page, it's probably what you used, and it says 0.7.0= at > nearly the same point as the other referenced page). > > Well, this explains (perhaps) why the port wasn't updated: the port = > author *could have* been fooled as I was. We (FreeBSD GNOME Team) were not fool by this. We knew that we should = update brasero to 0.6.x that time when it was stable release. Most of us= = are busy and brasero seems to be low priority in the plates. The other o= f = us don't know C/SCSI. Let's bring this topic back, shall we? ;-) Cheers, Mezz > Just so I either feel better, or can > castigate myself tonight, am I right, does that first page say what I = = > said > it did, or am I just going nuts? > >> >> > is at 0.5.1. Is it normal, so something like gnome utils (that so = = >> many >> > use) to follow the most recent version, of to follow the most recen= t >> > *stable* version? Note I'm not being fascetious, I really don't kn= ow >> > the >> >> Yeah, we normal do that. If we add development version then it would = be >> brasero-devel if we are interest to maintain it. Most of time we add = in >> MC CVS instead do *-devel unless it really need to be *-devel if it's= = >> not >> fit in GNOME release. >> >> Cheers, >> Mezz >> >> > answer, but maybe, if one would use the x11/gnome port as a guide, >> > well, it's running at version 2.20.2, which I think (unless I misre= ad >> > their website) is their stable release ... but they didn't actually= >> > seem to make >> > any distinction on that site, current versus stable. I still don't= >> > know, but I think that brasero shouldn't just be automatically be >> > updated to the >> > current version without deciding that, right? >> > >> > Or, should the port have a second one, a brasero-current, added? I= >> > know that either way, a update is needed, but that needed to be loo= ked >> > at, right? >> > >> >> Joe >> > >> > -----BEGIN PGP SIGNATURE----- >> > Version: GnuPG v2.0.4 (FreeBSD) >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> > >> > iD8DBQFHeqJyz62J6PPcoOkRAvI+AJ4vti44pUrrT0XUlkAX4VeMIWb96gCeOmZV >> > S0DuBM4q/Ar9Z1cDxnaDF/k=3D >> > =3DuMoU >> > -----END PGP SIGNATURE----- -- = mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org