=== Wulf4 is now known as Wulf === redwolf| is now known as redwolf [17:59] someone pinged? [18:00] Kamilion: you have build scripts for your images right? [18:00] https://github.com/kamilion/kamikazi-core/tree/master/buildscripts [18:00] sure do [18:00] ^^ Wulf there you go. not what ubuntu uses, but it's what someone else uses to make a custom image. [18:01] uses ubuntu-customizer to unpack the iso, the squashfs, then chroot inside. A hook script then (in my case) installs git, grabs that repo, and starts messing with packages and running scripts. [18:02] then the process is reversed, the kernel and initrd (and xen) are extracted from the rootfs, the rootfs is squashfs'd, and stuffed back on the .ISO. all the other files like the checksums and such are regenerated too. [18:02] it's inelegant, but it works. [18:03] right now, I do it in two steps [18:03] the first step is taking a release lubuntu image and trimming it [18:03] https://github.com/kamilion/kamikazi-core/blob/master/buildscripts/xenial/00-build-minilubuntu-iso-from-source.sh [18:04] which will replace firefox with qupzilla, and purge the 'unnessicary' desktop packages (for my use case; having a word processor on a server's desktop is not helpful, and because I use TORAM=YES, it's also a waste of memory. [18:04] also rip out most of the media libraries, but leave a couple 'standard' ones [18:05] so the browser can still play HTML5 video formats, but that's about it. [18:08] at a high level, I remove: apport, abiword, gnumeric, sylpheed, transmission, mtpaint, firefox, audacious, and light-locker. [18:08] at the moment, with all of that trimmed out and qt5 installed for qupzilla, the minilubuntu iso sits at 560.1MB [18:08] which is approximately 1.9GB of files compressed. [18:08] the ISO I build on top of that one ends up at 963.2GB, containing ~3.8GB of files compressed. [18:09] why don't you build it from scratch? it seems that was his primary interest, for some reason [18:09] but that's got the whole build system and kernel headers for the booted kernel and all the -dev packages for bunches of C libs that pip wants for building various things like uwsgi. [18:10] wxl: after talking to a lawyer, i was basically told that respinning the ISO was something canonical couldn't do anything about, as long as I didn't name my project *buntu. [18:11] Kamilion: what do you consider the disadvantages in starting from scratch, were that to have been a requirement? [18:13] i download the ISO over bittorrent, and use international package mirrors during my build process. [18:13] none [18:13] however, I ran into lots of problems getting a working configuration [18:13] because what's on the ISO isn't what's in the repository, nessicarily [18:13] and if you remove or purge the wrong thing, everything breaks. [18:15] I was never able to identify what it is in canonical's seed builder that makes things work, but the only thing I can think of is there's some scripts behind the scenes assembling things correctly there with all kinds of bugfix checks [18:15] for example, somewhere lubuntu makes some customizations to settings that aren't part of the packages themselves and I have *no idea where*. [18:15] did you check to see if release team publishes all that stuff? [18:16] when I debootstrap from scratch, I'm missing all kinds of configuration that, sets plymouth to use the lubuntu bootsplash, sets the default desktop session to load, basically anything having to do with alternatives *sucks* when you're rolling from scratch [18:16] it's perfectly adequate for rolling CLI stuff [18:19] but for having a working live environment 'just fire up' like lubuntu does, nothing beats working off the release ISOs. [18:19] you know everything is already in a sane configuration [18:19] and you can test packages being removed with synaptic to see if it breaks the running environment or screams about removing half the system [18:19] plus there's all sorts of other interactions, pulling in a package pulls in a bunch of libraries which enable functionality elsewhere, and then removing the package you installed doesn't remove the libraries which still have dependants [18:19] rabbitvcs is a good example of that [18:20] installing it will demand that *SOME* vcs it can control is around, and defaults to hg, last I checked, so one must install git before or during the same transaction... [18:20] so there's just all these weird corner cases that were solved somehow for the releases *shrug* [18:21] and another weird one, something keeps pulling in qt4-doc but doesn't really care if it's removed afterwards. That package doesn't compress well and inflates the ISO by about 100MB so one of the last things I do in my build process is remove it. [18:21] and make sure it's gone >.< [18:22] plus other little things like that; figuring out some optional package doesn't compress well (and sucks 8-14MB in with it) can be omitted [18:28] about the only thing lxqt needs to satisfy me is a port of the gnome-disks tool to QT [18:28] if I have that, I can live without all the rest of the gtk universe [21:59] has anyone looked at systemd performance in lubuntu versus other flavors? it seems i hear a lot of comments about boot time, but haven't necessarily heard this elsewhere [23:34] wxl: Hm, not sure. I'll look into it this weekend. [23:35] wxl: Also, @LubuntuOfficial (aka me) mentioned you in a tweet. :P [23:37] wxl: And @popey retweeted that tweet. [23:49] tsimonq2: let me know what you find out [23:49] tsimonq2: also OMG I AM FAMOUS [23:55] wxl: XD [23:55] wxl: Ok, will do. :)