| zequence | OvenWerks: It's best we make all of that configurable, in -controls, I think. Right now, i want to solve the bigger issues first - how we setup our DE. | 07:35 |
|---|---|---|
| zequence | I created a ubuntustudio-core seed | 10:18 |
| zequence | Ah, need to change the structure for our ISO too | 10:18 |
| zequence | Also, going to try get upload rights so we don't need sponsors for these uploads | 10:19 |
| zequence | We can continue to talk about what -core should contain. Right now, I simply moved all core type components from audio into a new seed file | 10:24 |
| zequence | Applying 16th of June. | 10:37 |
| OvenWerks | zequence: I agree about making it configurable and also about it not being something that should be added right now. | 13:04 |
| OvenWerks | I am experimenting just to see what works. | 13:04 |
| OvenWerks | I will have to start working with 14.10 directly though. The problem is that pulse (and some other things) are started before the xfce session manager by upstart. Upstart will not ship with 14.10 and I do not know if pulse will be started by systemd or something else. | 13:08 |
| OvenWerks | I did make a simple script that starts jackdbus, a2jmidid and then respawns pulse with some sleeps to make things work. I made everything I could think of a variable so that instead of setting it in the same script, it can be read in from a config file. | 13:12 |
| OvenWerks | Soon as the new ISO is up I will play with that though. I will look at the seeds after work. | 13:12 |
| zequence | OvenWerks: Sure. My plan is, ubuntustudio-controls is set to autostart, and will check what configs the user chose, then start processes from there | 15:20 |
| zequence | OvenWerks: I managed to cause mayhem in the Ubuntu germinate process for building the ISOs :P | 20:08 |
| zequence | last two commits to seeds were reverted | 20:08 |
| zequence | Seems like I need to dive my head into that again | 20:08 |
| OvenWerks | :) | 20:09 |
| OvenWerks | Ah, so everything ends up in one seed file. What does germinate do? I would guess it creates a list of packages/subseed files | 20:13 |
| OvenWerks | So germinate would have to be run twice? | 20:13 |
| OvenWerks | (once for each ISO) | 20:14 |
| OvenWerks | zequence: From what I can see I think the build script has to be changed along with the seeds. The script in the build package seems to have each ISO that may be built listed... or at least it looked that way. | 20:18 |
| zequence | OvenWerks: I think in this case it had to do with inheritance - the failure. I decided to do changes first, then ask someone to make sure we get an ISO | 20:21 |
| zequence | I need to learn how it all happens, so that one can test changes locally first | 20:21 |
| zequence | docs are pretty bad, of course | 20:21 |
| zequence | There is a bunch of info in ubuntu-cdimage, if I remember correctly | 20:23 |
| zequence | lp:ubuntu-cdimage | 20:23 |
| zequence | OvenWerks: Seems the big problem came down to me not declaring the new desktop-minimal in STRUCTURE. Will try again tomorrow | 21:14 |
| zequence | The seeds can be tested locally with germinate | 21:14 |
| zequence | Might be good to do that, especially when creating new seed files like I did | 21:15 |
| OvenWerks | zequence: from http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/README | 23:28 |
| DalekSec | zequence: Do you need any help? | 23:28 |
| OvenWerks | As you can see, it is possible to publish two sets of images into the same | 23:29 |
| OvenWerks | release directory, provided that they have different types (the "install" | 23:29 |
| OvenWerks | and "live" arguments). | 23:29 |
| OvenWerks | DalekSec: Ya, we want to create two versiohns of a live ISO | 23:29 |
| * OvenWerks must be using sausages for typing | 23:30 | |
| OvenWerks | It seems the README is quite old (2005), I am not sure that things actually still work the same way. | 23:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!