On Sat, Jul 14, 2007 at 07:00:23PM +0300, Alexey Suslikov wrote:
> On 7/14/07, Marc Espie <[EMAIL PROTECTED]> wrote:
> >On Sat, Jul 14, 2007 at 06:07:57PM +0300, Alexey Suslikov wrote:
> >> --- amarok/src/engine/xine/xine-engine.cpp.orig
> >> +++ amarok/src/engine/xine/xine-engine.cpp
> >> @@ -61,7 +61,7 @@
> >>
> >> ///returns the configuration we will use. there is no KInstance, so
> >> using this hacked up method.
> >> //static inline QCString configPath() { return
> >> QFile::encodeName(KStandardDirs().localkdedir() +
> >> KStandardDirs::kde_default("data") + "amarok/xine-config"); }
> >> -static inline QCString configPath() { return
> >> QFile::encodeName(locate( "data", "amarok/") + "xine-config" ); }
> >> +static inline QCString configPath() { return
> >> QFile::encodeName(QDir::homeDirPath() + "/.xine/config" ); }
> >> static Fader *s_fader = 0;
> >> static OutFader *s_outfader = 0;
> >
> >I think this is the kind of stuff you should discuss directly with the
> >amarok people, there is nothing OpenBSD-specific in there.
> >
> >I will accept this patch if they say it's okay.
>
> Thanks for reply.
>
> Kaffeine and xine-ui uses ~/.xine/config which is custom for me
> since I have 48KHz-only codec in my notebook.
>
> Amarok uses it's own xine-config which is uncomfortable. I think
> this is for good if all OpenBSD xine-lib dependant ports will use
> single config file. Especially in cases like mine.
but this is not how the original distribution works, and could
cause confusion.
> Separate xine-config file may be useful with ALSA or OSS but I
> don't know Linux well enough in this area.
it could possibly be useful on OpenBSD too. maybe someone wants
some special xine-lib features with Amarok and not with xine-ui?
as Marc says, please discuss this with the Amarok developers.
--
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org
