[M3devel] M3Config contains paths to installation directory.

[Dragiša Durić]

My question was about location and names of secondary config files. Are
these changed again? What would ne shipping procedure for compiler
installation? Something new there?

/cm3 is excellent idea, but on organized system (and if you package for
general public) some standard location is preferred. I will change my
locatio to /opt/cm3 now.

dd

On Fri, 2009-07-31 at 07:54 +0000, Jay K wrote:
> sorry /usr/local/cm3/bin -- or wherever cm3 is installed.
> I actually use just /cm3, but I often alter my examples to fit more common practise. Sometimes it helps confuse people less to use typical concrete paths instead of metata syntax. Esp. because puting less than and greater than around things causes hotmail to remove them, so lame, so tempting meta syntax doesn't work..
>  
> Just as /tmp/foo can be replaced by anything.
>  
>  - Jay
> 
> 
> ----------------------------------------
> > From: dragisha at m3w.org
> > To: jay.krell at cornell.edu
> > Date: Fri, 31 Jul 2009 09:47:37 +0200
> > CC: m3devel at elegosoft.com; eiserlohpp at yahoo.com
> > Subject: Re: [M3devel] M3Config contains paths to installation directory.
> >
> > On Fri, 2009-07-31 at 07:06 +0000, Jay K wrote:
> >> mkdir -p /tmp/foo/bin/config
> >> cd /tmp/foo/bin
> >> cp /usr/local/bin/cm3 .
> >> cp /usr/local/bin/cm3.cfg .
> >> cp /usr/local/bin/config/* config
> >> export PATH=/tmp/foo/bin:$PATH
> >
> > Please tell me /usr/local/bin/config/* is mistake here...
> > --
> > Dragiša Durić 
> >
-- 
Dragiša Durić <dragisha at m3w.org>