Mubuntu Metapackages Breakdown

It currently looks like Mubuntu will be made up of 3 packages + a 4th of the users choosing.

- Should Mubuntu be made up of 3 base packages + a 4th? The 4th being mubuntu-audio, mubuntu-video or mubuntu-graphics? The disk should be made up of the base 3 and what? - C.Kontros

mubuntu-desktop

Package to form the foundation of Mubuntu. This should retain as much of the Ubuntu admin functions as possible.

• Status -

mubuntu-artwork

Easy one. Package that contains all the Mubuntu artwork. Themes, wallpaper, icons etc...

• Status -

mubuntu-desktop-settings

This is for desktop settings.

• Status -

mubuntu-audio

All applications deemed nessessary to provide a working PC studio environment. This is the package most users of other derivatives will be interested in, so they don't get forced into a different desktop environment with a new theme and such.

• Status -

mubuntu-video

Video editing apps. List?

• Currently the state of "open" video editing seems to be lacking. There are some promising apps coming ([http://www.diva-project.org/ Diva]) but none seem to be at a really usable level yet. Am I mistaken? - C.KontrosBRBR

• You can have a look at this projetc, http://garbure.org/ . They made some live cds for multimedia, and one is for video editing. So just see the list of apps they use.

• Status -

mubuntu-graphics

A current, complete set of 2D/3D manipulation applications. ie: Inkscape, GIMP, Blender and so on. - I need to get some more opinions on this. - C.KontrosBRBR

• Status -

So, basicaly, we spoke about two meta-packages for the basics, one for common packages, and one for multiverse/restricted packages. I think we must do packages with the essential, and then, study the possibility to make other meta-packages for midi, video, etc... The idea it that not everybody as the same need of packages, so, perhaps the best way could be to organize meta-packages so that people can easily choose and install only what they need. I make a start of list here:

• Mubuntu -> install all the meta-packages below

• Mubuntu-basics
  • jackd (the jack daemon, one program "to rule them all")
  • qjacktcl (good gui to control jackd)
  • ardour (essential tool for audio recording)

  • ubuntustudiolauncher (launch applications in the good way for real time) --> this is a bad idea, IMO. LASH is the way to go. Realtime should be automatic anyhow.

• Mubuntu-multiverse
  • (start the list here)
• Mubuntu-soundwork
  • rezound (tool to edit wave)
  • jamin (mastering tool)
• Mubuntu-midi
  • rosegarden (good midi sequencer)
  • hydrogen (rythm sequencer)
  • seq24 (midi sequencer)
• Mubuntu-synth
  • ams (alsa modular synth)
  • zynaddsubfx (good synth)
• Mubuntu-effects
  • omins (set of ladspa effects)
  • tap-plugins (Tom Szilagyi's set of ladspa effects)
  • jack-rack (allow to make rack of ladspa effetc, patched in jack)
  • swh-plugins (Steve Harris’s set of ladspa effects)
  • mcp-plugins (for alsa modulat synth)
  • fil-plugins (set of ladspa effects)
  • cmt (set of ladspa effects)
  • caps (set of ladspa effects)

Don't hesitate to comment, complete the list, etc... Of course, that's just an idea. (ttoine)

- My thoughts on this are the fact that if I want to make music, I need the following: ardour, jack, seq24, zynaddsubfx, hydrogen at minimum. So to get these, I install the metapackages that contain them - mubuntu-basics, mubuntu-seq, mubuntu-mastering, etc. and I end up having EVERYTHING installed anyhow. So either we simply use one big package, or we use many packages that depend on different *sets* of applications. If I want seq24, I don't want Rosegarden. But installing a package how you have laid it out, I get both. I don't want both. Do you see the problem? If we get both, then the division into many smaller metapackages by type is just pointless. -DanaOlsonBRBR - Let me clarify what I mean by "sets of applications." My preferred combo is: seq24 + zynaddsubfx + hydrogen + ardour. Other people wouldn't want those, and they might choose: rosegarden4 + ams + specimen + ardour. That's what I mean. The problem is that there are infinite combinations. But having a metapackage contianing all sequencers, and one with all synths, etc just ends up with everything installed anyhow. I hope this is clearer. -DanaOlsonBRBR - Well... the only interest of separating by kind of application is that some people could be interested by only midi apps, some other by audio+midi apps, etc... My choice will be only audio apps, since I only work with real intruments and so don't need midi or synth. Perhaps we don't need to separate every kind of apps, but for sound engineers working in studios, it is important to provide a good solution wih selected audio apps, that they can test without having to install everything. It was in that way I started this list. If you think it is not important, so, I let it down. Also, there are tons of audio apps you are not accounting for... The list is here: http://ubuntustudio.com/wiki/index.php/Important_Audio_Software For packaging requests, I have that here: http://ubuntustudio.com/wiki/index.php/Software_Packaging_Efforts BRBR - I just want to make a precision : the idea was to ease testing of apps... I know that everyboy don't need the same set of applications.... and of course, that having the same kind of applications is not very util. But only the people who know the softs, like us, don't need meta-packages, since they know what to install. The Idea was to ease the installation of categories of softwares for beginners tests.BRBR - Beginners will want everything installed and make a choice by trying the software or following tutorials. I don't object to breaking them down further, but it's extra work for what will amount to nothing. New users don't know what they want, experienced users know how to get what they want, and they won't want to install every MIDI app via a metapackage. -DanaOlson

Comments