[cl-debian] Bug#384071: stumpwm: Please update to a more recent cvs checkout
Package: stumpwm Version: 1:20060513-1 Severity: wishlist -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-zedek Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15) Versions of packages stumpwm depends on: ii cl-clx-sbcl 0.7.2-1 An X11 Common Lisp client library ii cl-port 20060408-1 Common Lisp Object Collections Por ii common-lisp-controller 6.2 This is a Common Lisp source and c stumpwm recommends no packages. -- no debconf information
tags 384071 + pending thanks Hello Xavier! On Mon, 21 Aug 2006 20:03:09 +0200, Xavier Maillard wrote:
Version: 1:20060513-1 Severity: wishlist
I was waiting for the upload of 1:20060513-2, which corrects small Debian-related issues and the I'd upload a new CVS checkout, which is necessary because of the (long-awaited) support for modifiers other than Ctrl. I'm testing on my Debian a checkout made 2 days ago and I'm planning to ask to my sponsor to upload it next week (thus the pending tag). Thx, bye, Gismo / Luca
Processing commands for control@bugs.debian.org:
tags 384071 + pending Bug#384071: stumpwm: Please update to a more recent cvs checkout There were no tags set. Tags added: pending
thanks Stopping processing here.
Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Will you also include a cl-launch script to make stumpwm runnable easily from the command-line? As I said in a previous mail, you should use (after testing) something like BINARY=/usr/bin/stumpwm IMAGE=/usr/lib/sbcl/stumpwm.core SYSTEMS=/usr/share/common-lisp/systems LISPS="sbcl" DUMP="--dump ${IMAGE}" cl-launch --lisp "${LISPS}" \ --path ${SYSTEMS} --no-include \ --system stumpwm \ --init '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))' \ --wrap 'LISP=sbcl SBCL=/usr/bin/sbcl SBCL_OPTIONS=" " STY=' \ --output ${BINARY} \ ${DUMP} [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Mathematics is the Queen of Science but she isn't very Pure; she keeps having babies by handsome young upstarts and various frog princes. --Donald Kingsbury (In "psychohistorical crisis", 2001) On 23/08/06, Luca Capello <luca@pca.it> wrote:
I was waiting for the upload of 1:20060513-2, which corrects small Debian-related issues and the I'd upload a new CVS checkout, which is necessary because of the (long-awaited) support for modifiers other than Ctrl.
I'm testing on my Debian a checkout made 2 days ago and I'm planning to ask to my sponsor to upload it next week (thus the pending tag).
Hello Faré! On Wed, 23 Aug 2006 17:30:46 +0200, Faré wrote:
Will you also include a cl-launch script to make stumpwm runnable easily from the command-line?
I'm still sceptic about it, not because cl-launch, but because stumpwm is something surely not "easy" (check bug #356948 [1] for more informations). Moreover, I think we need to find a common way to specify cl-launch files. For example, stumpwm can be loaded through CMUCL or SBCL, thus the script in /usr/bin/stumpwm cannot have the SBCL option hardcoded (because files in /usr should not be edited by the administrator). Thus, we would need something in /etc/cl-launch/, but this needs a bit of brainstorming, before ;-)
As I said in a previous mail, you should use (after testing) something like
Thank you for the hint, I put it into the StumpWM ToDo list, to be considered as soon as we will have solved the "problems" above. However, I, for myself, prefer to load every time a fresh SBCL instead of a dumped imaged. I guess we need to provide both solutions. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356948
As I said in a previous mail, you should use (after testing) something like
Thank you for the hint, I put it into the StumpWM ToDo list, to be considered as soon as we will have solved the "problems" above. However, I, for myself, prefer to load every time a fresh SBCL instead of a dumped imaged. I guess we need to provide both solutions. 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. Xavier
Hello Xavier! On Thu, 24 Aug 2006 00:50:35 +0200, Xavier Maillard wrote:
Thank you for the hint, I put it into the StumpWM ToDo list, to be considered as soon as we will have solved the "problems" above. However, I, for myself, prefer to load every time a fresh SBCL instead of a dumped imaged. I guess we need to provide both solutions.
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. Moreover, as I track the CVS version, I don't need to dump a new image every time there's a new commit ;-) [OK, StumpWM has not a lot of commits, but just to explain you my idea] As I already stated, IMHO we should provide both solutions, maybe triggered by a command-line option ? Faré, what do you think about it? Thx, bye, Gismo / Luca
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
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
Hello Xavier! On Thu, 24 Aug 2006 18:08:28 +0200, Xavier Maillard wrote:
From: Luca Capello <luca@pca.it>
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 ?
This could be an idea, at least until bug #384697 [1] won't be solved. Moreover, this could be an improvement for bug #356948 [2].
Oh and by the way, do you maintaint a Debian repository where we could apt-get stumpwm "beta package" ?
Actually no, but you can track the darcs repository at [3]. Thx, bye, Gismo / Luca Footnotes: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384697 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356948 [3] http://cl-debian.alioth.debian.org/repository/lcapello/stumpwm
Moreover, I think we need to find a common way to specify cl-launch files. For example, stumpwm can be loaded through CMUCL or SBCL, thus the script in /usr/bin/stumpwm cannot have the SBCL option hardcoded (because files in /usr should not be edited by the administrator). You can normally pass --lisp "sbcl cmucl clisp" as an argument thus you can easily set LISPS="list of CL implentations separated by spaces". I personally used to use this when on Gentoo GNU/Linux: cl-launch --output ~/bin/mystumpwm --lisp "sbcl clisp" \ --system stumpwm --init '(stumpwm:stumpwm ":0")' Xavier
Your message dated Fri, 06 Oct 2006 11:48:10 +0200 with message-id <87irix22sl.fsf@gismo.pca.it> and subject line Bug#384071: stumpwm: Please update to a more recent cvs checkout has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
participants (4)
-
"Faré" -
Luca Capello -
owner＠bugs.debian.org -
Xavier Maillard