Re: [LAD] Interoperability between session management systems

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: J. Liles <malnourite@...>
Cc: <linux-audio-dev@...>
Date: Sunday, February 24, 2013 - 10:59 am

------DBGBC9KKH47VLTG92DSXS5238JCLAN
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=UTF-8

Do I realy need to explain to you for what a release is good for?
--
Diese=
Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.
=

"J. Liles" schrieb:

On Sat, Feb 23, 2013 at 9:=
13 PM, hermann meyer wrote:

Am 24.02.2013 06:02, schrieb=
J. Liles:

I stated it out already in a other thread: without ever been r=
eleased as NSM (means available as tarball, or what ever, with ONLY NSM inc=
luded), I wouldn't support it.

This is stupid. What difference does it m=
ake what other programs are in the source repository? Distributions can and=
should package the programs individually. Also, NSM clients require from t=
he NSM server implementation. There is no libnsm to link to etc. This is th=
e definition of a non-issue.

So be it for you.
For me, a session manageme=
nt which I will support in my projects, have to be released as such. Otherw=
ise I wouldn't waste my time with it. period.

You're not making any sens=
e. Why would I waste my time trying to make something which is already 100%=
modular and independent appear to be more so? You clearly have some rather=
fundamental misunderstanding of what's involved here. All Non-DAW etc have=
in common with NSM is that they share the same author and happen to work t=
ogether. If that's too much integration for you, well then you must have so=
me very strange motives.

------DBGBC9KKH47VLTG92DSXS5238JCLAN
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

=
Do I realy need to explain to you for what a release is good for?
=
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Ma=
il gesendet.

"J. Liles&quo=
t; <malnourite@gmail.com> schrieb:
On Sat, Feb 23, =
2013 at 9:13 PM, hermann meyer <brummer-@web.de> wrote:

=20
=20
=20

Am 24.02.2013 06:02, schrieb J. Liles:

I stated it out already =
in
a other thread: without ever been released as NSM (means
available as tarball, or what ever, with ONLY NSM included), I
wouldn't support it.

This is stupid. What difference does it make what other programs
are in the source repository? Distributions can and should
package the programs individually. Also, NSM clients require
from the NSM server implementation. There is no libnsm to link
to etc. This is the definition of a non-issue.

So be it for you.
For me, a session management which I will support in my projects,
have to be released as such. Otherwise I wouldn't waste my time wi=
th
it. period.

You're not making any sense. Why would I waste =
my time trying to make something which is already 100% modular and independ=
ent appear to be more so? You clearly have some rather fundamental misunder=
standing of what's involved here. All Non-DAW etc have in common with N=
SM is that they share the same author and happen to work together. If that&=
#39;s too much integration for you, well then you must have some very stran=
ge motives.

------DBGBC9KKH47VLTG92DSXS5238JCLAN--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] Interoperability between session management systems, Johannes Kroll, (Sat Feb 23, 4:01 pm)
Re: [LAD] Interoperability between session management systems, David Robillard, (Sat Feb 23, 11:36 pm)
Re: [LAD] Interoperability between session management systems, David Robillard, (Sat Feb 23, 11:45 pm)
Re: [LAD] Interoperability between session management systems, Roy Vegard Ovesen, (Sun Feb 24, 10:58 am)
Re: [LAD] Interoperability between session management systems, brummer-, (Sun Feb 24, 10:59 am)