Hello
The problem is what if I didn't want the program anymore? I'd have to look through half a dozen directories and remove related files, and still not know if I got them all. So I tried installing software into seperate folders using --prefix and --exec-prefix on the ./configure script. This made removing or upgrading programs a lot easier, but I'd have to symlink binaries and libraries.
Thats why I write down all changes I made on the system. like compile options, configure flags etc.
Most of the Gnu-Soft behaves okay und installs the files in well known directories. Most come
with a Makefile. There is a switch (was it -n?) that only print the commands before doing. I pipe the output into a file and look before installing where the files go. I backup this file. Okay, this takes time. Its worth.
A good place to look is /usr/local/{share,man,doc,bin,etc}. But I am sure you know that
Emacs e.g. behaves very well. Dont forget to backup the .emacs.d stuff and .emacs
LFS lets you optimize the software by compiling it, a distro like Red Hat doesn't optimize the software by compiling it but manages packages for when you want to upgrade or uninstall, but why I settled on Gentoo was because emerge compiles the software AND keeps track of what files go where for easy uninstall.
I did not use rpm, but read something about src.rpms. They contain all the information how to install somewhere/somehow. I didnt know emerge, too. But sounds good if a tracker could do this automation.
I have to say, that I didnt even know the ipk format, heard it looks similiar to the debian stuff.
I'd love to try out emacs on my C860 since as one of your arguments there isn't an IPK for it (and XEmacs is not the same). Maybe you can post a guide on how you did it and make it easy to update or uninstall in the future.
What pdaXrom needs is emerge and the portage tree ported to the Z!!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=72182\"][{POST_SNAPBACK}][/a][/div]
Uuh. Hard hit. As I mentioned above I write down all changes on the system, I talked about the desktop computer
I did not setup the whole zaurus system, just playing around so far. I could be wrong, but at this stage it needs great effort to compile the whole system. Look at the double grep binaries eg. autoconf issues.
It is worth if you can setup a base system from source like the lfs toolchain.
I never compiled a kernel for zaurus nor a gcc, not even autoconf by myself. I will try this next week.
So far it were only minor changes. Some links from zgcc image to /usr/lib/crt* (the c runtime stuff)
And there was a problem with a doubled grep. In /bin and in the zgcc Image is a grep. I removed /bin/grep. Hmm. LFS keeps track of such things. No wonder. The x86 community is much bigger there
I can remember the following
install texinfo (I did it from source, but a ipk might good here)
install perl (I used the ipk, too lazy to compile)
install libpcre (ipk)
maybe the order is wrong
emacs needs only the generic procedure: configure && make all && make install
Some things I really miss in the standard rom are bzip2, less (did both manually) and the updatedb/locate, whereis functionality. (next week)
And yes. I am a control freak too. Discover problems/bugs is fun in linux. Especially if you debug high level stuff.
The choice of my employer is windows. Because of the good support. The shiny area on the top of my head says more than thousand words.
Never mind
Enno
