diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20101218')
16 files changed, 284 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20101218/013dea1d/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/013dea1d/attachment-0001.html new file mode 100644 index 000000000..e566e230b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/013dea1d/attachment-0001.html @@ -0,0 +1,6 @@ +<br>Hello, just few words to mention the <span id="result_box" class="short_text" lang="en"><span title="Cliquer ici pour voir d'autres traductions" class="hps">obvious :<br><br>1. musicians are sub-group<br>2. RT-kernel need is a sub-sub-group of (electronic and music) needs<br> +3. Jack works well on normal-kernel now, providing 90% of sound-studio usages (really needs of -RT are rares, irl)<br><br>and last thing : kernel-RT is not suffisant. user must configure most things on system (limits.d, sysctl, acpi, tmpfs or ramfs, fstab, and more to have a "real pro-audio station like any others o.s"), so providing kernel-rt is good to seems give "out-of-the-box" possibility, but it lies : user in all cases must configure what is bad to auto-conf through spec file<br> +<br></span></span><span id="result_box" class="short_text" lang="en"><span title="Cliquer ici pour voir d'autres traductions" class="hps">So maybe it's a false good idea to provide kernel-rt.<br> +Another stone to wall "dont want to have many kernel in repo"<br><br>ps : the real trouble about sound-studio seems to be "how to provide non-free support" ? (eg : compil most softwares with mp3 support, and vst support) It is possible to provide this supports but without distribute the lib of ? example : compil qtractor with mp3 + vst support, but wihtout provide lib for mp3 and vst : software could but user need to install himself mp3 and vst ?<br> +<br>end of off-topic<br>nice night<br>maybe soon<br> +</span></span><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/013dea1d/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/013dea1d/attachment.html new file mode 100644 index 000000000..e566e230b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/013dea1d/attachment.html @@ -0,0 +1,6 @@ +<br>Hello, just few words to mention the <span id="result_box" class="short_text" lang="en"><span title="Cliquer ici pour voir d'autres traductions" class="hps">obvious :<br><br>1. musicians are sub-group<br>2. RT-kernel need is a sub-sub-group of (electronic and music) needs<br> +3. Jack works well on normal-kernel now, providing 90% of sound-studio usages (really needs of -RT are rares, irl)<br><br>and last thing : kernel-RT is not suffisant. user must configure most things on system (limits.d, sysctl, acpi, tmpfs or ramfs, fstab, and more to have a "real pro-audio station like any others o.s"), so providing kernel-rt is good to seems give "out-of-the-box" possibility, but it lies : user in all cases must configure what is bad to auto-conf through spec file<br> +<br></span></span><span id="result_box" class="short_text" lang="en"><span title="Cliquer ici pour voir d'autres traductions" class="hps">So maybe it's a false good idea to provide kernel-rt.<br> +Another stone to wall "dont want to have many kernel in repo"<br><br>ps : the real trouble about sound-studio seems to be "how to provide non-free support" ? (eg : compil most softwares with mp3 support, and vst support) It is possible to provide this supports but without distribute the lib of ? example : compil qtractor with mp3 + vst support, but wihtout provide lib for mp3 and vst : software could but user need to install himself mp3 and vst ?<br> +<br>end of off-topic<br>nice night<br>maybe soon<br> +</span></span><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/41cc1b3a/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/41cc1b3a/attachment-0001.html new file mode 100644 index 000000000..0cb5de049 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/41cc1b3a/attachment-0001.html @@ -0,0 +1,17 @@ +Hi <br><br><div class="gmail_quote">2010/12/18 yvan munoz <span dir="ltr"><<a href="mailto:mr.yvan.munoz@gmail.com">mr.yvan.munoz@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br>Hello, just few words to mention the <span lang="en"><span title="Cliquer ici pour voir d'autres traductions">obvious :<br><br>1. musicians are sub-group<br></span></span></blockquote><div>yes, but there are more and more musicians that want to use linux. Mainly IMHO cause ther was a wave of sound apps development started end 2009 / beginning 2010 that really makes linux more and more attractive to musicians, naming Qtractor, ladish and even some new native linux VSTs .. and new LV2 plugs.<br> + </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span lang="en"><span title="Cliquer ici pour voir d'autres traductions">2. RT-kernel need is a sub-sub-group of (electronic and music) needs<br> +</span></span></blockquote><div>yes, since kernel 2.6.33 the RT-Patch even made my system less stable that the normal kernel<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<span lang="en"><span title="Cliquer ici pour voir d'autres traductions"> +3. Jack works well on normal-kernel now, providing 90% of sound-studio usages (really needs of -RT are rares, irl)<br></span></span></blockquote><div>Well ... the normal kernel is o.k. exept, that it still has the "Tickles System" activated. Deaktivating this really boosts the kernel for sound .. at least in my and other cases I know it did.<br> +<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span lang="en"><span title="Cliquer ici pour voir d'autres traductions"><br> +and last thing : kernel-RT is not suffisant. user must configure most things on system (limits.d, sysctl, acpi, tmpfs or ramfs, fstab, and more to have a "real pro-audio station like any others o.s"), so providing kernel-rt is good to seems give "out-of-the-box" possibility, but it lies : user in all cases must configure what is bad to auto-conf through spec file<br> + +<br></span></span></blockquote><div>Therefore I like the idea of the wizard.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span lang="en"><span title="Cliquer ici pour voir d'autres traductions"></span></span><span lang="en"><span title="Cliquer ici pour voir d'autres traductions">So maybe it's a false good idea to provide kernel-rt.<br> + +Another stone to wall "dont want to have many kernel in repo"<br><br>ps : the real trouble about sound-studio seems to be "how to provide non-free support" ? (eg : compil most softwares with mp3 support, and vst support) It is possible to provide this supports but without distribute the lib of ? example : compil qtractor with mp3 + vst support, but wihtout provide lib for mp3 and vst : software could but user need to install himself mp3 and vst ?<br> + +<br></span></span></blockquote><div>Good point, but I have no answer to this at this point.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<span lang="en"><span title="Cliquer ici pour voir d'autres traductions">end of off-topic<br>nice night<br>maybe soon<br> +</span></span><br><br> +</blockquote></div>regards, saschas<br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/41cc1b3a/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/41cc1b3a/attachment.html new file mode 100644 index 000000000..0cb5de049 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/41cc1b3a/attachment.html @@ -0,0 +1,17 @@ +Hi <br><br><div class="gmail_quote">2010/12/18 yvan munoz <span dir="ltr"><<a href="mailto:mr.yvan.munoz@gmail.com">mr.yvan.munoz@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br>Hello, just few words to mention the <span lang="en"><span title="Cliquer ici pour voir d'autres traductions">obvious :<br><br>1. musicians are sub-group<br></span></span></blockquote><div>yes, but there are more and more musicians that want to use linux. Mainly IMHO cause ther was a wave of sound apps development started end 2009 / beginning 2010 that really makes linux more and more attractive to musicians, naming Qtractor, ladish and even some new native linux VSTs .. and new LV2 plugs.<br> + </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span lang="en"><span title="Cliquer ici pour voir d'autres traductions">2. RT-kernel need is a sub-sub-group of (electronic and music) needs<br> +</span></span></blockquote><div>yes, since kernel 2.6.33 the RT-Patch even made my system less stable that the normal kernel<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<span lang="en"><span title="Cliquer ici pour voir d'autres traductions"> +3. Jack works well on normal-kernel now, providing 90% of sound-studio usages (really needs of -RT are rares, irl)<br></span></span></blockquote><div>Well ... the normal kernel is o.k. exept, that it still has the "Tickles System" activated. Deaktivating this really boosts the kernel for sound .. at least in my and other cases I know it did.<br> +<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span lang="en"><span title="Cliquer ici pour voir d'autres traductions"><br> +and last thing : kernel-RT is not suffisant. user must configure most things on system (limits.d, sysctl, acpi, tmpfs or ramfs, fstab, and more to have a "real pro-audio station like any others o.s"), so providing kernel-rt is good to seems give "out-of-the-box" possibility, but it lies : user in all cases must configure what is bad to auto-conf through spec file<br> + +<br></span></span></blockquote><div>Therefore I like the idea of the wizard.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span lang="en"><span title="Cliquer ici pour voir d'autres traductions"></span></span><span lang="en"><span title="Cliquer ici pour voir d'autres traductions">So maybe it's a false good idea to provide kernel-rt.<br> + +Another stone to wall "dont want to have many kernel in repo"<br><br>ps : the real trouble about sound-studio seems to be "how to provide non-free support" ? (eg : compil most softwares with mp3 support, and vst support) It is possible to provide this supports but without distribute the lib of ? example : compil qtractor with mp3 + vst support, but wihtout provide lib for mp3 and vst : software could but user need to install himself mp3 and vst ?<br> + +<br></span></span></blockquote><div>Good point, but I have no answer to this at this point.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<span lang="en"><span title="Cliquer ici pour voir d'autres traductions">end of off-topic<br>nice night<br>maybe soon<br> +</span></span><br><br> +</blockquote></div>regards, saschas<br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/49e0c9df/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/49e0c9df/attachment-0001.html new file mode 100644 index 000000000..5d9253563 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/49e0c9df/attachment-0001.html @@ -0,0 +1,13 @@ +Read the tutorial and I think that this really is the best solution IMHO.<br>I mean providing a good wizard<br><br>1. check system can be included<br>2. modular installation of package groups or even single packages out of a group is possible<br> +3. alternation and adding files is possible - like limits.conf, etc. is possible<br><br>actually sounds perfect to me.<br><br>note to myself: RTFM perl<br><br>greetings, saschas<br><br><div class="gmail_quote">2010/12/18 Michael scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</a>></span><br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, Dec 18, 2010 at 08:01:19PM +0100, SaschaS wrote:<br> +> A wizard sounds like a good idea....<br> +><br> +> are there any howtos on Wizards for M??<br> +<br> +</div>yes, there is one dating back to my days at Mandrakesoft :<br> +<a href="http://wiki.mandriva.com/en/Development/Howto/WritingWizard" target="_blank">http://wiki.mandriva.com/en/Development/Howto/WritingWizard</a><br> +<br> +--<br> +<font color="#888888">Michael Scherer<br> +</font></blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/49e0c9df/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/49e0c9df/attachment.html new file mode 100644 index 000000000..5d9253563 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/49e0c9df/attachment.html @@ -0,0 +1,13 @@ +Read the tutorial and I think that this really is the best solution IMHO.<br>I mean providing a good wizard<br><br>1. check system can be included<br>2. modular installation of package groups or even single packages out of a group is possible<br> +3. alternation and adding files is possible - like limits.conf, etc. is possible<br><br>actually sounds perfect to me.<br><br>note to myself: RTFM perl<br><br>greetings, saschas<br><br><div class="gmail_quote">2010/12/18 Michael scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</a>></span><br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, Dec 18, 2010 at 08:01:19PM +0100, SaschaS wrote:<br> +> A wizard sounds like a good idea....<br> +><br> +> are there any howtos on Wizards for M??<br> +<br> +</div>yes, there is one dating back to my days at Mandrakesoft :<br> +<a href="http://wiki.mandriva.com/en/Development/Howto/WritingWizard" target="_blank">http://wiki.mandriva.com/en/Development/Howto/WritingWizard</a><br> +<br> +--<br> +<font color="#888888">Michael Scherer<br> +</font></blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/49fedb5f/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/49fedb5f/attachment-0001.html new file mode 100644 index 000000000..6c397e2fa --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/49fedb5f/attachment-0001.html @@ -0,0 +1,15 @@ +<br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr"><<a href="mailto:herman@aeronetworks.ca">herman@aeronetworks.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br> +On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br> +> I'm here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br> + +> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br> +><br> +> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br> +IMHO the most important thing is to make a basic package that works.<br> +The user can then add other things they like. As things are, it is very<br> +difficult for an ordinary mortal to make a working sound system by<br> +installing individual packages.<br> +<br> +</blockquote></div><br>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br> +<br>And maybe we can also make a similar task for the creators out there?<br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/49fedb5f/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/49fedb5f/attachment.html new file mode 100644 index 000000000..6c397e2fa --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/49fedb5f/attachment.html @@ -0,0 +1,15 @@ +<br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr"><<a href="mailto:herman@aeronetworks.ca">herman@aeronetworks.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br> +On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br> +> I'm here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br> + +> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br> +><br> +> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br> +IMHO the most important thing is to make a basic package that works.<br> +The user can then add other things they like. As things are, it is very<br> +difficult for an ordinary mortal to make a working sound system by<br> +installing individual packages.<br> +<br> +</blockquote></div><br>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br> +<br>And maybe we can also make a similar task for the creators out there?<br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/6d1a951c/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/6d1a951c/attachment-0001.html new file mode 100644 index 000000000..9aeef011f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/6d1a951c/attachment-0001.html @@ -0,0 +1,7 @@ +<br><br><div class="gmail_quote">2010/12/18 SaschaS <span dir="ltr"><<a href="mailto:ungleichklang@gmail.com">ungleichklang@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +2. modular installation of package groups or even single packages out of a group is possible<br></blockquote><div><br>This is the work of drakrpm (of preferably Kpackagekit) no ?<br>Â <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> + +3. alternation and adding files is possible - like limits.conf, etc. is possible<br></blockquote><div><br>yes :-) <br></div><div>Â </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +actually sounds perfect to me.<br><br>note to myself: RTFM perl<br></blockquote><div><br>i tried, it s more complicated as wiki says. You could read what Aginies write for it's old ssh wizard ("simple" example)<br> +Â <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">greetings, saschas<br><br></blockquote><div>Providing a shell script could a way to have a clean and release early, often thing to do that ? what thing about ? <br> +</div></div> diff --git a/zarb-ml/mageia-dev/attachments/20101218/6d1a951c/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/6d1a951c/attachment.html new file mode 100644 index 000000000..9aeef011f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/6d1a951c/attachment.html @@ -0,0 +1,7 @@ +<br><br><div class="gmail_quote">2010/12/18 SaschaS <span dir="ltr"><<a href="mailto:ungleichklang@gmail.com">ungleichklang@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +2. modular installation of package groups or even single packages out of a group is possible<br></blockquote><div><br>This is the work of drakrpm (of preferably Kpackagekit) no ?<br>Â <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> + +3. alternation and adding files is possible - like limits.conf, etc. is possible<br></blockquote><div><br>yes :-) <br></div><div>Â </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +actually sounds perfect to me.<br><br>note to myself: RTFM perl<br></blockquote><div><br>i tried, it s more complicated as wiki says. You could read what Aginies write for it's old ssh wizard ("simple" example)<br> +Â <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">greetings, saschas<br><br></blockquote><div>Providing a shell script could a way to have a clean and release early, often thing to do that ? what thing about ? <br> +</div></div> diff --git a/zarb-ml/mageia-dev/attachments/20101218/880f7aaa/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/880f7aaa/attachment-0001.html new file mode 100644 index 000000000..0def3c75e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/880f7aaa/attachment-0001.html @@ -0,0 +1,21 @@ +So I see basically that we need a guidline on how mageia deals with Spinoffs first.<br><br>If all task are in the repos, I can understand those who say that there are to many task.<br>If the spinoffs are handled as separate projects, we could provide a cusom .iso and different sound-tasks, that people download from the spinoff page.<br> +The a<br><br><div class="gmail_quote">2010/12/18 Daniel Kreuter <span dir="ltr"><<a href="mailto:daniel.kreuter85@googlemail.com">daniel.kreuter85@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr"><<a href="mailto:herman@aeronetworks.ca" target="_blank">herman@aeronetworks.ca</a>></span> wrote:<br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br> +On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br> +> I'm here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br> + + +> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br> +><br> +> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br> +IMHO the most important thing is to make a basic package that works.<br> +The user can then add other things they like. As things are, it is very<br> +difficult for an ordinary mortal to make a working sound system by<br> +installing individual packages.<br> +<br> +</blockquote></div><br></div></div>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br> + +<br>And maybe we can also make a similar task for the creators out there?<div><div></div><div class="h5"><br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> +</div></div></blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/880f7aaa/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/880f7aaa/attachment.html new file mode 100644 index 000000000..0def3c75e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/880f7aaa/attachment.html @@ -0,0 +1,21 @@ +So I see basically that we need a guidline on how mageia deals with Spinoffs first.<br><br>If all task are in the repos, I can understand those who say that there are to many task.<br>If the spinoffs are handled as separate projects, we could provide a cusom .iso and different sound-tasks, that people download from the spinoff page.<br> +The a<br><br><div class="gmail_quote">2010/12/18 Daniel Kreuter <span dir="ltr"><<a href="mailto:daniel.kreuter85@googlemail.com">daniel.kreuter85@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr"><<a href="mailto:herman@aeronetworks.ca" target="_blank">herman@aeronetworks.ca</a>></span> wrote:<br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br> +On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br> +> I'm here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br> + + +> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br> +><br> +> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br> +IMHO the most important thing is to make a basic package that works.<br> +The user can then add other things they like. As things are, it is very<br> +difficult for an ordinary mortal to make a working sound system by<br> +installing individual packages.<br> +<br> +</blockquote></div><br></div></div>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br> + +<br>And maybe we can also make a similar task for the creators out there?<div><div></div><div class="h5"><br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> +</div></div></blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment-0001.html new file mode 100644 index 000000000..c5ed04e17 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment-0001.html @@ -0,0 +1,28 @@ +.... sorry, my little son found the send button ....<br><br>That way we could provide something for nearly every need.<br>We even could offer separate kernels.<br><br>But first lets see how we can integrate the idea of spinoffs into the mageia projekt.<br> +<br>greetings, Sascha<br><br><div class="gmail_quote">2010/12/18 SaschaS <span dir="ltr"><<a href="mailto:ungleichklang@gmail.com">ungleichklang@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +So I see basically that we need a guidline on how mageia deals with Spinoffs first.<br><br>If all task are in the repos, I can understand those who say that there are to many task.<br>If the spinoffs are handled as separate projects, we could provide a cusom .iso and different sound-tasks, that people download from the spinoff page.<br> + +The a<br><br><div class="gmail_quote">2010/12/18 Daniel Kreuter <span dir="ltr"><<a href="mailto:daniel.kreuter85@googlemail.com" target="_blank">daniel.kreuter85@googlemail.com</a>></span><div><div></div><div class="h5"> +<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<div><div></div><div><br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr"><<a href="mailto:herman@aeronetworks.ca" target="_blank">herman@aeronetworks.ca</a>></span> wrote:<br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br> +On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br> +> I'm here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br> + + + +> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br> +><br> +> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br> +IMHO the most important thing is to make a basic package that works.<br> +The user can then add other things they like. As things are, it is very<br> +difficult for an ordinary mortal to make a working sound system by<br> +installing individual packages.<br> +<br> +</blockquote></div><br></div></div>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br> + + +<br>And maybe we can also make a similar task for the creators out there?<div><div></div><div><br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> +</div></div></blockquote></div></div></div><br> +</blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment.html new file mode 100644 index 000000000..c5ed04e17 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment.html @@ -0,0 +1,28 @@ +.... sorry, my little son found the send button ....<br><br>That way we could provide something for nearly every need.<br>We even could offer separate kernels.<br><br>But first lets see how we can integrate the idea of spinoffs into the mageia projekt.<br> +<br>greetings, Sascha<br><br><div class="gmail_quote">2010/12/18 SaschaS <span dir="ltr"><<a href="mailto:ungleichklang@gmail.com">ungleichklang@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +So I see basically that we need a guidline on how mageia deals with Spinoffs first.<br><br>If all task are in the repos, I can understand those who say that there are to many task.<br>If the spinoffs are handled as separate projects, we could provide a cusom .iso and different sound-tasks, that people download from the spinoff page.<br> + +The a<br><br><div class="gmail_quote">2010/12/18 Daniel Kreuter <span dir="ltr"><<a href="mailto:daniel.kreuter85@googlemail.com" target="_blank">daniel.kreuter85@googlemail.com</a>></span><div><div></div><div class="h5"> +<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<div><div></div><div><br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr"><<a href="mailto:herman@aeronetworks.ca" target="_blank">herman@aeronetworks.ca</a>></span> wrote:<br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<br> +On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br> +> I'm here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br> + + + +> But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br> +><br> +> I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br> +IMHO the most important thing is to make a basic package that works.<br> +The user can then add other things they like. As things are, it is very<br> +difficult for an ordinary mortal to make a working sound system by<br> +installing individual packages.<br> +<br> +</blockquote></div><br></div></div>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br> + + +<br>And maybe we can also make a similar task for the creators out there?<div><div></div><div><br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> +</div></div></blockquote></div></div></div><br> +</blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment-0001.html new file mode 100644 index 000000000..b54488226 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment-0001.html @@ -0,0 +1,35 @@ +A wizard sounds like a good idea....<br><br>are there any howtos on Wizards for M??<br><br>greetings, sascha<br><br><div class="gmail_quote">2010/12/18 Michael scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</a>></span><br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, Dec 18, 2010 at 10:03:36AM +0100, SaschaS wrote:<br> +> So I see basically that we need a guidline on how mageia deals with Spinoffs<br> +> first.<br> +><br> +> If all task are in the repos, I can understand those who say that there are<br> +> to many task.<br> +<br> +</div>The problem is not that there is too much more than the consequence of the<br> +high number of task-*.<br> +<br> +rpmdrake, who is the main consumer of task-* rpm<br> +convention, show all of them as 1 single list. So basically, with lots of tasks-<br> +rpm, you just have a big unsorted list of category. Obviously not good for endusers.<br> +<br> +While it would be useful to group task into sound category, for the moment,<br> +we cannot. One way would be to encode this information in the name ( ie, decide<br> +that task-sound-foo and task-sound-bar are part of the sound category ).<br> +<br> +I am not sure that using the name for this is a good idea. It is quite poor,<br> +in term of metadata, and that's still a tree structure, while may a tag based<br> +one may be better ( like Debian do, for example ).<br> +<br> +More ever, it doesn't make much sense to have task-lamp-* task-nagios and task-kde4<br> +at the same level, they are not destined at the same public.<br> +<br> +Not to mention that installing rpm is ust half of the solution, configuration is<br> +the other one. While we can to some extend push configuration in the rpm, there<br> +is some that we cannot do reliably ( like adding a user to a group ).<br> +<br> +So maybe a wizard is a better solution than using a rpm that does magically everything.<br> +<br> +--<br> +<font color="#888888">Michael Scherer<br> +</font></blockquote></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html new file mode 100644 index 000000000..b54488226 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html @@ -0,0 +1,35 @@ +A wizard sounds like a good idea....<br><br>are there any howtos on Wizards for M??<br><br>greetings, sascha<br><br><div class="gmail_quote">2010/12/18 Michael scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</a>></span><br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, Dec 18, 2010 at 10:03:36AM +0100, SaschaS wrote:<br> +> So I see basically that we need a guidline on how mageia deals with Spinoffs<br> +> first.<br> +><br> +> If all task are in the repos, I can understand those who say that there are<br> +> to many task.<br> +<br> +</div>The problem is not that there is too much more than the consequence of the<br> +high number of task-*.<br> +<br> +rpmdrake, who is the main consumer of task-* rpm<br> +convention, show all of them as 1 single list. So basically, with lots of tasks-<br> +rpm, you just have a big unsorted list of category. Obviously not good for endusers.<br> +<br> +While it would be useful to group task into sound category, for the moment,<br> +we cannot. One way would be to encode this information in the name ( ie, decide<br> +that task-sound-foo and task-sound-bar are part of the sound category ).<br> +<br> +I am not sure that using the name for this is a good idea. It is quite poor,<br> +in term of metadata, and that's still a tree structure, while may a tag based<br> +one may be better ( like Debian do, for example ).<br> +<br> +More ever, it doesn't make much sense to have task-lamp-* task-nagios and task-kde4<br> +at the same level, they are not destined at the same public.<br> +<br> +Not to mention that installing rpm is ust half of the solution, configuration is<br> +the other one. While we can to some extend push configuration in the rpm, there<br> +is some that we cannot do reliably ( like adding a user to a group ).<br> +<br> +So maybe a wizard is a better solution than using a rpm that does magically everything.<br> +<br> +--<br> +<font color="#888888">Michael Scherer<br> +</font></blockquote></div><br> |