| === shtylman__ is now known as shtylman | ||
| shtylman | corp186: https://wiki.ubuntu.com/Installer/Development?action=show&redirect=InstallerDevelopment that should get you started | 04:43 |
|---|---|---|
| shtylman | the branch is located at: https://code.launchpad.net/~ubuntu-installer/ubiquity/trunk | 04:43 |
| shtylman | you can ignore the IRC notification bits | 04:44 |
| shtylman | and to build the package after you make changes: run debuild | 04:44 |
| shtylman | more commonly, we just have a virtual machine and make the changes in that so we can test them quicker | 04:45 |
| corp186 | shtylman: I've been poring over that info, but I'm still a little lost | 14:09 |
| corp186 | how do I create a new installation iso | 14:09 |
| corp186 | I checked out the dists branch of debian-installer | 14:10 |
| corp186 | and checked out all the relevant packages | 14:10 |
| corp186 | then I used the debian instructions to try to build installation media | 14:10 |
| corp186 | like "fakeroot make build_cdrom_isolinux" | 14:11 |
| corp186 | but it ends up making a tarball, and not an iso | 14:11 |
| shtylman | corp186: why do you want to make a whole new iso? | 16:10 |
| corp186 | shtylman: maybe I don't need to, but I want to test changes to the installer | 16:11 |
| corp186 | so how can I make changes and test them? | 16:11 |
| shtylman | for development and testing you don't need to make a whole new iso, you can just boot a live environment and install your created deb into that | 16:11 |
| corp186 | I don't understand, but there are many holes in my understanding of how the installer works | 16:12 |
| shtylman | or... as I suggest, have a live environment (or even an installed system) in a virtual machine. Then install the ubiquity package in that system | 16:12 |
| shtylman | corp186: you can run the ubiquity installer from and installed system, it does not have to be from a live CD | 16:13 |
| corp186 | I think I see what you're getting at, so I have further questions | 16:13 |
| shtylman | k | 16:13 |
| corp186 | I'm having a hard time understanding how the d-i installer is put together | 16:13 |
| corp186 | from what I can tell, the installer runs programs from a series of packages | 16:14 |
| corp186 | if that's correct, where is the data that strings it all together in the right order | 16:14 |
| shtylman | I am not too familiar with d-i itself (my work is mainly in the frontend) but yes... there are a number of scripts that ubiquity calls out to | 16:14 |
| corp186 | I'm looking at modifying the underlying installation, not ubiquity (yet) | 16:15 |
| shtylman | the people to ask (they are not online right now) are cjwatson who has been working on the installer for a long time and also evand who works and maintails ubiquity currently | 16:15 |
| corp186 | shtylman: thanks | 16:15 |
| shtylman | np | 16:16 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!