Hi, > I'm looking into Pure:Dyne as a basis for creating a live-USB (or CD) - > bootable version of a SuperCollider based application. > > I already found some useful info here: > http://code.goto10.org/projects/puredyne/wiki/DocAutoBoot > (nice to see that it cites some of my own scripting ;) ). > > But, for my application I will also need some packages that are not in the > basic pure:dyne package (as far as I can see here > http://code.goto10.org/projects/puredyne/wiki/DocListApps), such as GNUPlot > and SwingOSC. > There's also quite a few applications that I wouldn't need, so I could leave > these out, to save some space. > > I found instructions here > http://code.goto10.org/projects/puredyne/wiki/LiveHelper > to build a live distro, and I assume I'll be able to configure the right > packages there. > However the link on that page to the pure:dyne live-helper config doesn't > work > anymore. Where can I find the new version? > > I'm also thankful for any other hints to help me make this all work.
We (/me pokes Aymeric :)) have done some work on simplifying this process of creating custom iso's through a script that takes care of everything. Its called 'broth', as traditional soup base should be and can be found here: https://code.goto10.org/viewcvs/index.cgi/puredyne/live/trunk/broth This already works quite well, but for the love of god I can't remember what was the process of setting it up (there has to be a directory in $HOME called 'puredyne-build' but maybe that gets created by broth.sh, aymeric?). In any case, in principle, the most interesting directory is the stock subdir, where a lot of custom hooks, files and debs can be put that are in no other repo or so. For instance, if you don't want most applications p:d comes with you can start editing the files in: broth/stock/chroot_local-packageslists/ Similarly, if you want to include a package that is not in the repo you can simply put it (and its dependencies, if they are not in Debian or our repos) into this dir and they get installed: broth/stock/chroot_local-packages/ In case you want to add specific user-based configuration files you can do this by adding them into the this subdir: stock/chroot_local-includes/etc/skel/ From there they will get copied to the user's $HOME dir. I'm sure there is much more to say, especially about the hooks that can be used for weird situations or hacks, but I'm not really a pro on this subject (yet :) and the documentation is far from existant (at least to my knowledge). Let us know what are your experiences with this! Greetings, Karsten -- karsten gebbert -- krgn.goto10.org
signature.asc
Description: Digital signature
--- [email protected] irc.goto10.org #pure:dyne
