On 2012-01-25 15:08:03 (+0200), Stathis Agrapidis <stathisagrapidis(a)gmail.com>
On Tue, Jan 24, 2012 at 3:36 AM, Pascal Bleser
> On 2012-01-23 17:46:12 (-0600), Bryen M Yunashko <suserocks(a)bryen.com> wrote:
>> On Mon, 2012-01-23 at 23:32 +0100, Pascal Bleser wrote:
>> Maybe Studio guys figured it was okay to use Packman, but only if you
>> don't make it publicly available via the Gallery? Or only if the
>> builder makes sure to not include patent-infringing packages regardless
>> of public or private consumption. (But how does the average builder
>> know which package is "verboten"?)
> True, that is probably allowed: building with
Studio but not
> hosting it in the Studio Gallery.
> That means that it would require some
infrastructure of its own,
> at the very least to host the images.
Maybe if the repository gets included but the softwate
with the patent
problems isn't installed by default then it shouldn't be a legal
problem, but I am not really sure about it.
It would still be a patent problem, doesn't make a difference.
The issue here is primarily to host and provide the packages.
It doesn't require that people install it :)
The other thing that was discussed in the oSC in
September was the
pattern thing. For starters we could create a pattern including all
audio related software or at least a choice of audio applications.
Then with a 1-click installer it should be really easy to transform
the default installation to an audio installation. That as a fist
step. Then we can see how that goes and proceed with a spin.
Hmh. I think it's more complicated than that.
If you want a setup for audio, you _definitely_ want to use jack
instead of alsa or pulseaudio. And that requires a lot of
fiddling around in config files to get it to work.
I managed to get most stuff to work properly, but it's quite a
lot of config file hacks, in many applications.
Oh, and everything KDE is very difficult as well, but that's
already the case with pulseaudio (vlc backend is discontinued
and doesn't work properly with pulse anyway, mplayer backend is
unmaintained and can't even be compiled, the vlc backend works,
but needs configuring vlc (not necessarily intuitive) to select
the sound backend + it lags when you move around in a song in
amarok, and gstreamer... well... it's gstreamer...).
So simply transforming a setup into something that is
appropriate for using audio applications (such as mixxx, etc...)
cannot be simply done through installing software.
It also requires modifying a lot of configuration files.
-o) Pascal Bleser
-- we haz green
-- we haz conf