Hi there, Karsten Gebbert said : > > 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.
karsten: I thought SwingOSC and GNUPlot were in p:d ... Actually I'm sure SwingOSC is. > > 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? this is obsolete, we need to clean the wiki! > > 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?). It should create it if it's not found. But it still lacks a check for needed deb packages required (from build essentials to lh stuff). This needs to be done manually. > 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). Yes, the main idea behind broth is to provide an easy way to branch/fork/remix pure:dyne using our "vanilla" setup as default but with the freedom to customize easily everything from desktop wallpaper to installed software without having to get into details. It could be used for anything like making a proper free p:d with a libre kernel and no binary blobs, add a last minute package for a workshop/install/perf, distribute a customized or rebranded p:d, etc... It's also the 1st step towards a multi architecture building system... even though we're still far from there ;) It's working very well at the moment and we built the last alpha and dev isos using it. The only problem is that leek and potato was not built with broth but directly using lh, you can find all the config here: http://code.goto10.org/projects/puredyne/browser/live/tags/puredyne-1.0-leek_and_potato/config BUT this was based using a non final lh release, the same config will break today if you run lh with this config. So I would suggest you try to build your image based on the coming new p:d, carrot and coriander, for which broth has been created and which is working with the latest lh snapshots. Next step is to document broth and release it. This is one of the biggest priority for the coming sprint in august. Meanwhile, if anybody wants to try or contribute to it, please feel free and ask help or give suggestions on the list. and yes .... patches welcome ;) > Let us know what are your experiences with this! oui oui :) a. --- [email protected] irc.goto10.org #pure:dyne
