> Sorry, I miscommunicated: the server *only* serves as memory for the clients. > I.e., the clients fetch the binary from the server, that's all.
I don't understand at all this kind of architecture. Are you speaking of thin-clients here or why must fricas be moved to the server if at runtime the binary will again be copied to the client. Sounds very strange. > And I misread: I do not compile the code on the server, since it will never > run > there. What you have communicated so far let's me think that the fricas code simply lives on some disk partition that is mounted on the client. Why is the server relevant at all? >>> If you know how to do configure and makefiles, maybe you could add a rule to >>> install fricas*.el, when emacs is present... >> Martin, as I said before, I won't add any rule that installs anything outside >> $prefix. So please tell me exactly what you want to have and where you want >> it to live. > Hm, how do other packages that come with an emacs mode do things? Sorry, I have no idea. All of the packages that you listed in your mail went to /usr/share/emacs/sitelisp probably because the Debian people configured the .deb package that way. As I said, that is OK, but for "make install" without any additional specific options I simply think that installing outside $prefix is not right. (I am not the wisest guru in this field so anybody is invited to prove me wrong.) >> As I said in my previous mail, I would simply put fricas*.el under SVN into >> >> trunk/src/emacs/fricas*.el >> >> and install them (not depending on whether emacs is there or not) into >> (compare src/aldor/Makefile.in) >> install_target_dir = $(DESTDIR)$(libdir)/fricas/target/$(target) >> install_emacs_dir = $(install_target_dir)/emacs > > But then I will have to tell emacs where to find them, which is non-trivial > for > non-emacs users. OK. You can probably tell emacs users what to do. If you want to promote fricas in emacs also for non-emacs-users then perhaps there is another way. I don't know exactly, but can one start emacs with giving it a path to a (maybe different than ~/.emacs) init file? At least you can give a elisp expression on the emacs command line. So my suggestion would be: provide a script efricas which starts emacs with some "(setq load-path ...) (require 'fricas) (start-fricas)" on the command line. Then there is no need to install anywhere outside $prefix. If you want to have some hints, maybe you ask the Singluar people. They had something like a esingular. I think also cocoa followed this track. And finally, why don't you suggest running Axiom inside Firefox? Start sage and switch to "Axiom" as standard. Ralf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/fricas-devel?hl=en -~----------~----~----~----~------~----~------~--~---
