Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Dec 2017 13:12:05 +0800
From:      blubee blubeeme <gurenchan@gmail.com>
To:        Sid <sid@bsdmail.com>
Cc:        FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   Re: Canberra
Message-ID:  <CALM2mEne4MhqbtJSYxHvPuezOwnU6Gr5CYOKt0nNPcxPxWaEwA@mail.gmail.com>
In-Reply-To: <trinity-71ed6d20-8a22-4f42-9553-e8c22732fa0c-1513659164997@3c-app-mailcom-lxa03>
References:  <trinity-11ecd798-3177-4f2c-8f38-140493210fe1-1513649994492@3c-app-mailcom-lxa01> <CALM2mEmEvYOZic=qwnS%2BKV1HhEZGOjmTrh%2B3xoKEnPVrHzgW5g@mail.gmail.com> <trinity-71ed6d20-8a22-4f42-9553-e8c22732fa0c-1513659164997@3c-app-mailcom-lxa03>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 19, 2017 at 12:52 PM, Sid <sid@bsdmail.com> wrote:

> devel/pycanberra
>
> audio/freedesktop-sound-theme hasn't been tested for most ports that ask
> for libcanberra, and I haven't tried it on any port yet either. The source
> for pycanberra may need patches to work with freedesktop-sound-theme. You
> could include both as options. If they conflict, you'll have to use
> OPTIONS_RADIO (single choice). In any case, libcanberra should drop gtk
> requirements, but they may be reluctant to do so. pycanberra's name implies
> it's for libcanberra.
>
> IMO, it's better to clean up as many ports before flavors comes along,
> because then, there will be more excuses to not remove bloat.
>
> blubee blubeeme; Tue Dec 19 03:01:07 UTC 2017
> > quick question, I am porting py-canberra which isn't required but an
> optional dependency for another port that I am working on.
> > ibus-cangjie.
>
> > The ibus-cangjie port needs py-gobject anyways; so a whole lot of gtk
> stuff gets pulled in.
> > I wonder should I leave it as is or make a dependency from this thing
> you're working on instead?
>
> > I was waiting for @flavors to calm down before I started working on the
> port again.
>
> >> Canberra is an audio application for playing simple sounds like "DING!".
> >> For playing sound, I am convinced that graphical dependencies for
> audio/libcanberra and audio/libcanberra-gtk3 aren't needed:
> x11-toolkits/gtk30, x11-toolkits/gtk20, accessibility/atk.
> >> According to Freshports, both libcanberra and libcanberra-gtk3 refer to
> the file libcanberra-0.30.tar.xz of the same SHA256 and size.
> >> The difference between these two is one pulls in gtk3 as well.
>
> >> Pango is for left to right text, perhaps for displaying audio
> information to the user.
> >> Its description is its "code is platform- and toolkit-independent."
> >> For it to display a simple banner or visual it shouldn't require heavy
> graphical dependencies.
> >> Also, Pango should be made into an option for Canberra, so it can
> definitely be compiled without atk, gtk30 or gtk20.
> >> Pango doesn't require these three graphical dependencies, so Canberra
> especially shouldn't.
> >> USE_GNOME should also be a Makefile option in ports that are only about
> sound (libraries, applications, audio server components) and not graphics.
>
> >> libcanberra and libcanberra-gtk3 should be replaced with
> audio/freedesktop-sound-theme.
> >> Pango appears to be a different implementation of Bango, which is not
> in ports, but here: https://www.freedesktop.org/wiki/Bango/[https://www.
> freedesktop.org/wiki/Bango/].
>

py-canberra is just a python wrapper for libcanberra, I agree that ports
should be cleaned.
I'll get back to that in the coming days, I have some soldering and other
things keeping me a bit
tied up atm.



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