Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Nov 2004 17:53:53 -0600
From:      "Jeremy Messenger" <mezz7@cox.net>
To:        damian@indignation.org
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: Want to play w/ Coaster? Here's a port of it.
Message-ID:  <opshdlz3ab9aq2h7@mezz.mezzweb.com>
In-Reply-To: <1100292463.7873.20.camel@pompey.indignation.org>
References:  <opshchovvj9aq2h7@mezz.mezzweb.com> <1100292463.7873.20.camel@pompey.indignation.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Nov 2004 12:47:43 -0800, Damian <damian@indignation.org> wrote:

> Please excuse my faulty coherence/setup, I've noticed a few emails from
> this list didn't make it back to me due to my mail box crashing and a
> few responses regarding this topic were made. Anyways, coaster looks
> like a very promising burning app from gnome. It'd be quite a loss not
> to make it part of the freebsd-gnome "suite". Many people I speak to who
> run freebsd and gnome have to resort to the painstaking task of using
> k3b which depends on qt,kdelibs, and friends. Of course there is the
> problem with the author temporarily supporting nautilus-burn. I'm not
> quite sure how long this phase will last, but if they made such a
> transition, is it safe to say it will last more than a few months?
> Afterall, the work of porting their app to use a new backend seems
> pretty painstaking if their problems with libburn will be resolved
> fairly quickly. They could have just halted development and waited if it
> was coming in a short time. I've sent an email to the coaster-devel list

Where did you send coaster-devel list? At sourceforge? The author has  
closed at sourceforge and moved to GNOME's mailing list.  
http://www.coaster-burn.org/development.html

In future, please break your a very long paragraph into few paragraphs to  
make easier to read and easier to reply.

Cheers,
Mezz

> regarding this issue. I'd really like coaster to come aboard to freebsd,
> but it'd be pretty futile to port such an app and later be abandoned by
> its authors for the libburn backend. So I guess my question regarding
> the debate of adding coaster to ports is, how long will this
> "transition" last and would it be of benefit for freebsd to embrace it
> while it lasts (if very long)?
>
> Damian
>
>
> On Fri, 2004-11-12 at 03:23 -0600, Jeremy Messenger wrote:
>> Hello,
>>
>> I have created Coaster port: http://www.coaster-burn.org .. I haven't
>> tweak some stuff yet such as change default /var/tmp/ to ~/.coaster/ for
>> the ISO create like what I did with the nautilus-cd-burner. I am not  
>> going
>> to learn C++, so I am going to let someone w/ C++ knowledge to take care
>> of it. Anyway, beside the /var/tmp/, it works great so far for me.
>>
>> You will have to install bakery-devel first, which I made a repo copy  
>> from
>> bakery.
>>
>> http://people.freebsd.org/~mezz/shar/bakery-devel.shar
>> http://people.freebsd.org/~mezz/shar/coaster.shar
>>
>> I don't know if I should put coaster in the ports tree yet, because
>> current it depends on nautilus-cd-burner for temporary and later the
>> author will switch back to libburn/libcoaster when those get stable with
>> the newer Linux kernel. I personal have no idea how will libburn will  
>> work
>> with FreeBSD as I haven't done any of homework.
>>
>> BTW: A hint for hack of change /var/tmp/ to ~/.coaster/, I believe it's  
>> in
>> ${WRKSRC}/src/backends/nautilus.cc ..
>>
>> Have fun!
>>
>> Cheers,
>> Mezz


-- 
mezz7@cox.net  -  mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opshdlz3ab9aq2h7>