> > Hm. > I remember when I did it last time that it was a loooonnnnggggg > odyssey finding out which libraries were needed, finding > the libraries, finding other libraries from which the libraries > depend and so on. For newbies, this was definitely not an > acceptable way. The reason why I write and publish my own howtos > is exactly this: The experts throw one-liners like > "./configure --prefix=/usr && make deb-inplace" around and say > how easy all is, and then you sit there and nothing works, > because the experts forgot to say that there are concepts > like "dependencies". > > Thank you for your hint. I will test this line next time: > ./configure --prefix=/usr && make deb-inplace > > But even if this one line will work, I will have to document > it, because some kind of knowledge is not easy to find > in the Internet.
I've been compiling my own fvwm debian packages for some time and here are some additional hints. For dependencies the ones in Manjo's package are somewhat sane (as in they will work unless you care enough to limit some of them, you can install them all wth a single apt-get command) you can just type apt-get build-dep fvwm You may need/want to install build-essential as well. as for using 'make deb-inplace', it makes a .deb file just fine and it should install on your system (Works here for me on debian sid). This is old and outdated and a newer debian/ dir should be used to be more in line with the newer debian specification and I belive thomas did some work on this and has a newer debian/ on his git server, though I never have gotten around to trying it to compile a debian package. The last note is the debian package for some reason (I am still unsure why Manjo did this) has an epoch version and the package you made will not. Because of this epoch version the version in the debian repos 1:2.5.30 is considered greater than the version you compiled 2.6.3 for instance, and if you upgrade/dist-upgrade you system it will install the version from the debian repo effectivally downgrading your fvwm package. To prevent this you need to put the fvwm package on hold echo "fvwm hold" | dpkg --set-selections For those other fvwm debain users out there I hope this is of some help jaimos
