Ralf Hemmecke <[EMAIL PROTECTED]> writes:

> Hi Martin,
> 
> On 10/17/2008 08:43 PM, Martin Rubey wrote:
> > Ralf Hemmecke <[EMAIL PROTECTED]> writes:
> > 
> >>> The procedure here worked as follows:
> >>> * compile (as ordinary user) on a user machine
> >>> * copy it to a server machine (which has different architecture) with 
> >>> special
> >>>   priviledges (I'm not sure whether root was enough here)
> >>> * make install on the server machine.
> >> Sounds not like a big problem to me.
> >>
> >> A)
> >> 1. Login (as mrubey) on the server machine.
> >> 2. svn co https://fricas.svn.sourceforge.net/svnroot/fricas/trunk fricas
> >> 3. cd fricas && ./configure && make
> > 
> > no no: server is a different architecture...
> 
> Heh? What does that mean "different architecture". Under A) you compile 
> on the server machine so where do you see a problem?

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.

And I misread: I do not compile the code on the server, since it will never run
there.

> > It's just an inconvenience, no big problem.  In the case at hand, I did
> > 
> > cd fri-build
> > /home/rubey/fricas/configure 
> > make
> > 
> > (i.e., I called configure with an absolute path.  since that path is mounted
> > also on the server machine, make install worked there.)
> 
> What path? /home/rubey/fricas?

Yes.

> > There are certainly more severe problems.
> > 
> > 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?

> 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.  Since fricas.el doesn't require any emacs knowledge (although
it certainly helps), this is not so good.  (That's also the reason for the
existence of efricas)

If I look into my /usr/share/emacs/sitelisp, I find:

auctex autoconf csh-mode.el debian-startup.el dictionaries-common nxml-mode
psvn.el

or

auctex autoconf debian-startup.el dictionaries-common mmm-mode noweb-mode.el
psvn.el tramp

or even

a2ps.el ger-keys.elc php-mode.elc rubydb2x.el suse-start-preview-latex.el
vt200-esc-fix.el a2ps.elc idna.el po-compat.el rubydb3x.el suse-start-psgml.el
vt200-esc-fix.elc a2ps-print.el idutils.el po-mode.el ruby-electric.el
suse-start-python-mode.el web-mode.el a2ps-print.elc idutils.elc
preview-latex.el ruby-mode.el suse-start-uim.el web-mode.elc anthy inf-ruby.el
psgml site-start.el suse-start-xslide.el xfonts.el auctex maple.el psvn.el
start-po.el tex-site.el xfonts.elc auctex.el maple.elc punycode.el subdirs.el
timecard-mode.el xslide cweb.el mgp-mode20.el python-mode.el
suse-start-anthy.el timecard-mode.elc cweb.elc mgp-mode20.elc python-mode.elc
suse-start-auctex.el timidity.el desktop-entry-mode.el nxml-mode rmailgen.el
suse-start-nxml-mode.el t-mouse.el ger-keys.el php-mode.el rmailgen.elc
suse-start-po-mode.el uim-el

I wonder whether these modes have been put there all individually.

> So what exactly is your wish.

I want that the user has to do as little as possible manually.

Martin


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to