[09:43] Who is the -devel list manager? [09:43] * abogani waves all [09:43] :-) [09:46] jussi: Three lines above ^^^^ [09:46] 0/ [09:47] abogani: I am, as well as ScottL [09:47] jussi: Could you un-block my last email in -devel, please? [09:48] done [09:48] jussi: Thanks! [11:59] abogani, if no one volunteers to make the one-page kernel wiki page, then i will do it for you :) [12:39] ScottL: You are already too much involved into too much things ;) [12:46] 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] :) [13:18] 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] 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] 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] TheMuso: you might also know of some available documentation or information about creating tasks within the metapackages [16:18] morning all :) [16:20] paultag: morning to you [16:20] abogani, How are you today? [16:22] paultag: fine and you? [16:22] abogani, not too bad. A bit busy, but not bad at all. :) [16:23] :-) [16:46] hi paultag and abogani [16:46] scott-work, morning(?) :) [16:47] paultag: almost noon [16:47] scott-work, ah, you're EST as well :) [16:48] paultag: well, cst actually, so it's almost 11:00 ;) [16:48] Oh, well shucks [16:48] It's 15 minutes to noon here :) [16:48] i didn't want to differeniate that much usually because many are eurporean or asia :) [16:49] :) [16:49] i usually take lunch around 11:30 though, or whenever i find a convenient stopping point, or i'm just hungry ;) [16:49] 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] scott-work, what line of work are you in? [16:54] paultag: i am the detailing supervisor for an aluminum cover company - http://www.conservatek.com/ [16:54] scott-work, kickass [16:55] 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] there may be a time in the future where i may have that position thrust back upon me though :P [16:55] :) [17:14] * holstein is a jazz musician abogani [17:14] you too? [17:14] abogani: i will also try and have a look at the kernel wiki you put together soon [17:14] and help out [18:33] 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] 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] please correct me if my understanding is incorrect [18:35] i suppose another way to say it, if we define the desired tasks in our metapackage, the rest is handled automagickly ;) [19:12] oh, and i understand the magic carrot (^) i believe [21:45] persia: now i understand your previous concern about too many tasks and using tasksel [21:47] 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] scott-work: In Ubuntu's case, for the disks anyway, tasks are generated from seeds. [21:50] 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] TheMuso: i have them in front of me [21:50] each defines one task in the file [21:50] But then if we add tasks, we need to patch the disk build process to add the new tasks to the list. [21:50] scott-work: RIght [21:51] atm the tasks we see are limited to only what we want, so every new task requires touching things at two places. [21:51] i saw that we would need to add a .desc file under /share/blah/tasksel to be included [21:51] No. [21:51] i worried that the README was wrong about this (think it was probably for debian) [21:52] Yes, its for Debian. [21:52] okay, i also saw that we should file a bug report to add the task [21:52] this is for ubuntu? [21:53] Yes [21:54] We don't need to file a bug to add tasks to the disks. [21:54] where are the two places that are touched for every new tasks? [21:54] We just need to contact Colin to ask him to add new tasks to the limit lists. [21:55] 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] 2. We add the new task to the limit list for Ubuntu Studio in the disk build code. [21:55] right, that makes sense [21:55] we define it in the meta and colin adds it to the list [21:56] i understand that if we are installing the package the task must be listed elsewhere for tasksel to install it [21:56] Once the above 2 steps are done, the disk build process takes care of the rest. [21:57] so, we _could_ define numerous tasks within the metapackage, but only include the necessary ones for installing the appropriate metapackages [21:57] in the limit list [21:59] 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] I don't know, haven't thought about it. [22:01] i originally thought we would make new metapackages, one per "task" (in this case ubuntustudio-audio-recording, -generating, etc) [22:02] Right, wouldn't that be overwhelming? [22:04] 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] (sorry was talking to coworker) yes, quite overwhelming [22:05] In our situation, you would have to create more metapackages if you want more tasks. [22:06] oh :( so we cannot incorporate more than one task per metapackage ? [22:07] * scott-work apologizes if he's being dense [22:07] No we can't. [22:08] okay, then we are back to creating more metapackages (one per tasks) if we want to seperate the audio packages [22:09] which would be -base, -recording, -generating (maybe -performance) as we are expecting https://wiki.ubuntu.com/UbuntuStudio/PackageSelectionDevelopment [22:14] Right. [22:15] how difficult will it be to get new metapackages accepted into the archives? [22:17] Not very difficult at all. [22:17] 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] good :) [22:24] the proccess now doesn't seem to complicated and i am excited to begin it :P [22:31] 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] Right. [22:45] it gave me an error where it said it couldn't find the debootstrap [22:56] Right, you need to install the debootstrap and germinate packages. [22:57] ah, thanks