Menu
▾
▴
Re: [PyWM-talk] Stuck with the install
|
From: <el...@ji...> - 2006-03-19 20:49:28
|
cga wrote: > Elmo Mäntynen wrote: > >> cga wrote: >> >> >>> >> > [...] > >>> Please advise. >>> >>> >> >> Well, I don't know wether you looked in the README and or the INSTALL >> files (wich you should), but here are the parts that are applicable: >> >> " >> *** INSTALLING BINARY PACKAGE >> >> >> > [...] > > misread the instructions.. :-[ > > here's what I have: > > * There is no binary offered in this package, and there's > a version mismatch with python 2.3.5 and later, so building > from source is encouraged. I'll gladly help, or might even > send a binary if asked nicely=). If you'd like to try > the old binary, it's in the original 0.1 release (caution: the > instructions below > might not be correct). The "caution" is there for good reason=). I think they are reminiscent of some previous shape of pywm. > > * If you feel impatient, or you just hate building > stuff from source, you could try the binary module > included in this package. > > found this a little confusing.. at first glance (2) .. > > "try the binary module included in 'this' package.." appears to > contradict (1) "There is no binary offered in 'this' package.." I have made only the most necessary changes to the docs so it's possible to get started without going through everything I did the first time. Now that someone has shown interest I will definitely rework the docs. > > But I was not so much being 'impatient' & trying to comlete the > install so as to have a working pywm.. main objective was playing with > the install to clarify my understanding of pywm in relation to my > working environment.. the implications.. how it would fit into my > current setup - I obviously need to keep separate.. figuring whether > it would be preferable to run pywm under a test user.. the environment > variables I might need to set.. clarify the role of pyrex.. stuff like > that.. > >> So you do need libfltk1.1-dev and python-pyrex >> > python-pyrex is not installed but there is a debian package: > > $ apt-cache search pyrex > pyrex-mode - Emacs-lisp pyrex-mode for Pyrex > python-pyrex - Compile native-code modules for Python from python-like > syntax > python-tables - hierarchical database for Python based on HDF5 > python2.2-pyrex - Compile native-code modules for Python from > python-like syntax > python2.2-tables - hierarchical database for Python based on HDF5 > python2.3-pyrex - Compile native-code modules for Python from > python-like syntax > python2.3-tables - hierarchical database for Python based on HDF5 > python2.4-tables - hierarchical database for Python based on HDF5 I should've been clearer. I mean't, debian packages libfltk1.1-dev and python-pyrex, needed for compiling > > I do have a libfltk: > > $ dkg -l '*libfltk*' > .. > ii libfltk1.1c102 > 1.1.6-5 Fast Light Toolkit > shared libraries > > presumably installed when I 'apt-got' flwm. > >> (this might not be enough, >> we'll see), but you have no use for flwm >> > isn't flwm a requirement..? PyWM is an pythonisation of flwm, which you couldn't achieve by making a driver for the flwm binary. So, flwm isn't required, it's included (think of pywm as a fork of flwm). > >> (if you wan't a prebuilt binary, >> that's not the place where to look for it). >> >> >> > I try not to install too much stuff that's not managed by the debian > packaging system.. but for something like pywm that is not finalized > at this point - and not available in .deb -----------------------------------------------------------------------------------------------^^^^^^^^^^^^^^^^^^^^^ To be changed in the foreseeable future... > format - my instincts tell me that sooner or later I will have to > build from source. So I will have to keep track of what I install > manually - no big deal since there is not really much - but also.. and > that's my main concern.. make sure that components (libraries.. python > modules..) that are installed together with pywm do not clash with > anything that comes with the sarge distro.. That's why I would prefer > to use whatever components are already available on my system and *if > possible* get those that are not yet installed from debian > repositories. I do realize that you may not be able to advise me > regarding debian aspects and that I will have to figure this out myself. You just described my attitude towards non-debianized software, though I happen to use some devel versions of certain packages, which can be a bit of a pain with debian sometimes. So, I do use "the greatest distro of them all" (testing), and can help accordingly. Just installing pywm is very unlikely to clash with anything (no packages that I know of install anything having pywm somewhere in the path) > just hope I won't end up having to set up some form of chroot environment > > :-) About setting up a chroot: I currently run pywm inside a chroot, mainly because of ease of testing (I can use the same user without messing with my homedir) with some confidence that if X doesn't take the kernel with it if it happened to crash, my main instance of X isn't bothered. You can read the warning text at pywm.sf.net/#status, which is written by the original author. PyWM seems quite stable, but at least while developing your own scripts (am going to develop something generally useful, but in the meantime this is a necessary step for pywm to be of any real use), you should be vary about having open anything critical apps. Doing a "New login" and logging in as a different user would propably work without much fear of crashing your working environment, but you never know... >> " >> ... >> If you have successfully [built and] installed FLTK, you >> can log in as root and type: >> make install (or 'python setup.py build', and link to >> it by means of a site.py, etc) >> >> If the make completes successfully, you will have: >> >> * The PYWM launcher utility, installed as >> /usr/bin/pywm-run.py >> This program pops up a window of available window >> manager scripts, as well as an xterm fallback >> * The directory 'pywm' installed in your Python >> site-packages directory. Note that within this pywm >> directory is a copy of the examples directory. >> ... >> " >> >> This should work, but tell me if the instructions aren't clear >> enough(they aren't complete nor completely right, I have to work on >> that). >> >> >> >> > I need to send some time reading and understanding the instructions > regarding the source install and I will get back to you with any > questions I may have. Hopefully, this will provide a log of the > problems - if any - encountered by an average user with some > superficial knowledge of window managers.. little python and even less > oop.. and may help improve the INSTALL document. All this is hopefully going to improve, but you can always learn by figuring things out yourself. At least that has happened to me while working on pywm, since I didn't (and still don't) really know much about stuff like the build process of c/c++/pyrex, wm's and the debian way of generating menus and starting a particular wm through gdm... > Thank you very much for you fast, detailed response. > > Chris. Thanks for your interest, it's good to have someone else testing the install process, and better yet when I get to releasing .debs... Elmo |
