We could very well have several versions of stumpwm generated by cl-launch, and a master-script that accepts options and picks the right one depending on those options, and/or a /etc/alternatives/ thingie to select which version to pick. Personally, I when I use stumpwm, I don't usually dump image, because I re-launch it with twiddled sources more often than I start it from stable sources. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Merely having an open mind is nothing; the object of opening the mind, as of opening the mouth, is to shut it again on something solid. -- G.K. Chesterton On 24/08/06, Xavier Maillard <zedek@gnu.org> wrote:
Yo Luca,
From: Luca Capello <luca@pca.it>
Is not this too long each time ? I was quite sceptic about dumping an image too but it really speeds things up (a lot) at startup.
Well, I never tested a dumped image and in my case I don't care at all about the startup speed, because as I'm a massive user of suspend-to-disk (sometime suspend-to-ram, too), I don't reboot my laptop (and consequently my X) so often.
Lucky you. Here too I massively use s2d but stumpwm (or lisp implementation) often freezes here ;)
[snip]
As I already stated, IMHO we should provide both solutions, maybe triggered by a command-line option ? Far=C3=A9, what do you think about it?
I am not against that idea. Maybe just adding this information into README.Debian can be enough or just display something when installing the Debian package ?
Oh and by the way, do you maintaint a Debian repository where we could apt-get stumpwm "beta package" ?
Xavier