[09:43] <abogani> Who is the -devel list manager?
[09:43]  * abogani waves all
[09:43] <abogani> :-)
[09:46] <abogani> jussi: Three lines above ^^^^
[09:46] <jussi> 0/
[09:47] <jussi> abogani: I am, as well as ScottL
[09:47] <abogani> jussi: Could you un-block my last email in -devel, please?
[09:48] <jussi> done
[09:48] <abogani> jussi: Thanks!
[11:59] <ScottL> abogani, if no one volunteers to make the one-page kernel wiki page, then i will do it for you :)
[12:39] <abogani> ScottL: You are already too much involved into too much things ;)
[12:46] <scott-work> abogani: oh, i see you already made the wiki page...sorry i wasn't fast enough
[12:46]  * scott-work has just read his email
[12:49] <abogani> :)
[13:18] <scott-work> i signed up for open week to have an open Q&A about ubuntu studio
[13:19]  * scott-work wonders how many people will show up to ask questions
[14:22] <scott-work> persia: at some point in the relative near future we should begin to talk about updating the seeds, meta-packages, and adding tasks
[15:30] <scott-work> persia: do you have any links to anything i can start reading about tasks within the metapackages, my initial google searches have been pretty fruitless
[15:33] <scott-work> TheMuso: you might also know of some available documentation or information about creating tasks within the metapackages
[16:18] <paultag> morning all :)
[16:20] <abogani> paultag: morning to you
[16:20] <paultag> abogani, How are you today?
[16:22] <abogani> paultag: fine and you?
[16:22] <paultag> abogani, not too bad. A bit busy, but not bad at all. :)
[16:23] <abogani> :-)
[16:46] <scott-work> hi paultag and abogani 
[16:46] <paultag> scott-work, morning(?) :)
[16:47] <scott-work> paultag:  almost noon
[16:47] <paultag> scott-work, ah, you're EST as well :)
[16:48] <scott-work> paultag: well, cst actually, so it's almost 11:00 ;)
[16:48] <paultag> Oh, well shucks
[16:48] <paultag> It's 15 minutes to noon here :)
[16:48] <scott-work> i didn't want to differeniate that much usually because many are eurporean or asia :)
[16:49] <paultag> :)
[16:49] <scott-work> i usually take lunch around 11:30 though, or whenever i find a convenient stopping point, or i'm just hungry ;)
[16:49] <paultag> scott-work, mmm, for sure -- I'm over in Cleveland right now ( Boston by birth ;) )
[16:49]  * scott-work usually eats lunch at his desk to get ubuntu studio stuff done
[16:49] <paultag> scott-work, what line of work are you in?
[16:54] <scott-work> paultag: i am the detailing supervisor for an aluminum cover company - http://www.conservatek.com/
[16:54] <paultag> scott-work, kickass
[16:55] <scott-work> although i for a period of time i was acting engineering suerpvisor as well, coordinating with the rest of the company but not making any structural decisions
[16:55] <scott-work> there may be a time in the future where i may have that position thrust back upon me though :P
[16:55] <paultag> :)
[17:14]  * holstein is a jazz musician abogani 
[17:14] <holstein> you too?
[17:14] <holstein> abogani: i will also try and have a look at the kernel wiki you put together soon
[17:14] <holstein> and help out
[18:33] <scott-work> persia, TheMuso: i found a README in the tasksel package that i believe explains the task definition format - http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/tasksel/maverick/annotate/head%3A/README
[18:34] <scott-work> from what i have seen, i am also presuming that if we define the tasks in the metapackage (e.g. ubuntustudio-audio) then this will aggregate into the ubuntu-tasks.desc file installed by tasksel
[18:35] <scott-work> please correct me if my understanding is incorrect
[18:35] <scott-work> i suppose another way to say it, if we define the desired tasks in our metapackage, the rest is handled automagickly ;)
[19:12] <scott-work> oh, and i understand the magic carrot (^) i believe
[21:45] <scott-work> persia: now i understand your previous concern about too many tasks and using tasksel
[21:47] <scott-work> it would appear that if we defined numerous tasks within the metapackage (e.g. ubuntustudio-audio-editsong, ubuntustudio-audio-recordinstruments, ubuntustudio-audio-playmusic) each one of these tasks would be presented in the tasksel menu during installation
[21:49] <TheMuso> scott-work: In Ubuntu's case, for the disks anyway, tasks are generated from seeds.
[21:50] <TheMuso> SO you need to put a special few fields at the top of seed files to do this. Just look at the desktop file or the audio file in the bzr branch.
[21:50] <scott-work> TheMuso: i have them in front of me
[21:50] <scott-work> each defines one task in the file
[21:50] <TheMuso> But then if we add tasks, we need to patch the disk build process to add the new tasks to the list.
[21:50] <TheMuso> scott-work: RIght
[21:51] <TheMuso> atm the tasks we see are limited to only what we want, so every new task requires touching things at two places.
[21:51] <scott-work> i saw that we would need to add a .desc file under /share/blah/tasksel to be included
[21:51] <TheMuso> No.
[21:51] <scott-work> i worried that the README was wrong about this (think it was probably for debian)
[21:52] <TheMuso> Yes, its for Debian.
[21:52] <scott-work> okay, i also saw that we should file a bug report to add the task
[21:52] <scott-work> this is for ubuntu?
[21:53] <TheMuso> Yes
[21:54] <TheMuso> We don't  need to file a bug to add tasks to the disks.
[21:54] <scott-work> where are the two places that are touched for every new tasks?
[21:54] <TheMuso> We just need to contact Colin to ask him to add new tasks to the limit lists.
[21:55] <TheMuso> 1. We create a new seed file in the bzr branch, with appropriate fields at the top, as well as a list of packages we want that task/package to depend on.
[21:55] <TheMuso> 2. We add the new task to the limit list for Ubuntu Studio in the disk build code.
[21:55] <scott-work> right, that makes sense
[21:55] <scott-work> we define it in the meta and colin adds it to the list
[21:56] <scott-work> i understand that if we are installing the package the task must be listed elsewhere for tasksel to install it
[21:56] <TheMuso> Once the above 2 steps are done, the disk build process takes care of the rest.
[21:57] <scott-work> so, we _could_ define numerous tasks within the metapackage, but only include the necessary ones for installing the appropriate metapackages
[21:57] <scott-work> in the limit list
[21:59] <scott-work> TheMuso: how would you recommend updating the audio metapackage for separating into -recording, -generating, -common (and maybe -performance)?  just make tasks within the -audio package and remove the ubuntustudio-audio task from the list and add the former?
[22:00] <TheMuso> I don't know, haven't thought about it.
[22:01] <scott-work> i originally thought we would make new metapackages, one per "task" (in this case ubuntustudio-audio-recording, -generating, etc)
[22:02] <TheMuso> Right, wouldn't that be overwhelming?
[22:04] <scott-work> but after learning about tasks today i would think keeping the metas as they are and arranging tasks within them would be a better way :)
[22:04] <scott-work> (sorry was talking to coworker) yes, quite overwhelming
[22:05] <TheMuso> In our situation, you would have to create more metapackages if you want more tasks.
[22:06] <scott-work> oh :( so we cannot incorporate more than one task per metapackage ?
[22:07]  * scott-work apologizes if he's being dense
[22:07] <TheMuso> No we can't.
[22:08] <scott-work> okay, then we are back to creating more metapackages (one per tasks) if we want to seperate the audio packages
[22:09] <scott-work> which would be -base, -recording, -generating (maybe -performance) as we are expecting  https://wiki.ubuntu.com/UbuntuStudio/PackageSelectionDevelopment
[22:14] <TheMuso> Right.
[22:15] <scott-work> how difficult will it be to get new metapackages accepted into the archives?
[22:17] <TheMuso> Not very difficult at all.
[22:17] <TheMuso> Just a matter of creating files in the bzr branch, adding definitions to the ubuntustudio-meta package, and if tasks are wanted, going through the above.
[22:18] <scott-work> good :)
[22:24] <scott-work> the proccess now doesn't seem to complicated and i am excited to begin it :P
[22:31] <scott-work> TheMuso: although i had trouble last time trying to update the metapackage with persia :(  (not trying to imply that it was persia's fault mind you)
[22:31] <TheMuso> Right.
[22:45] <scott-work> it gave me an error where it said it couldn't find the debootstrap
[22:56] <TheMuso> Right, you need to install the debootstrap and germinate packages.
[22:57] <scott-work> ah, thanks