Re: First version of MinGW octave

[Paul Kienzle]

The problem with symlinks is that NSIS doesn't know about them, so
I have to recreate them after install.  I did this by hand for 2.1.50,
and wanted to automate it in future.  Not impossible by any stretch,
but I find I have less time available for Octave as time goes on.

        - Paul

On Feb 15, 2006, at 11:49 PM, Shai Ayal wrote:

> What is the issue with symbolic links? I was under the impression that
> cygwin emulates these
>
> Shai
>
> On 2/16/06, Paul Kienzle <address@hidden> wrote:
> > On Feb 15, 2006, at 11:56 AM, John W. Eaton wrote:
> >
> > > On 15-Feb-2006, Shai Ayal wrote:
> > >
> > > | that's what I though and what prompted me to develop octplot under
> > > | cygwin. Also discussed previously on the list, it is possible to 
> > > ship
> > > | a custom made cygwin1.dll with a prepackaged version of octave 
> > > which
> > > | will make it independent of the other parts of cygwin, which window
> > > | users are reluctant to install.
> > >
> > > I think this is generally discouraged by the Cygwin developers.  
> > > Also,
> > > it makes you the maintainer of your own version of Cygwin, and tends
> > > to annoy the Cygwin developers if your users start complaining about
> > > problems they are having with your custom cygwin1.dll on the Cygwin
> > > lists.
> >
> > Also, this breaks if you try to run octave and cygwin simultaneously.
> > Windows sees that both are called cygwin1.dll and so only loads one
> > of them.
> >
> > This and the symbolic links are the reason I didn't release a new
> > version of the octave installer.
> >
> > - Paul