On 18/03/2008, David Bateman <[EMAIL PROTECTED]> wrote:
> The nine inactive developers were:
> aadler ...
I would prefer not to be removed. I have a number
of contributions on my 'todo' list, which I
keep on thinking I'll find the time to do.
--
Andy Adler
-
On 18/03/08 22:59 +0100, David Bateman wrote:
> thomas-weber
Removing me is fine.
Thomas
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/g
After the recent large number of developer additions to octave-forge we
now now 43 developers registered. As has been traditional I therefore
think its time to strip the number of developers back to those that have
been active in the last year. As we changed to SVN since the last time
we did this t
tir, 18 03 2008 kl. 12:00 -0600, skrev Daniel J Sebald:
> dbateman wrote:
> > Seems fine to me (at least looking at it) and it shouldn't affect the other
> > functionality, so why not commit it..
> >
> > Cheers
> > D.
>
> Søren Hauberg wrote:
> >>I would be willing to integrate it into octave-fo
dbateman wrote:
> Seems fine to me (at least looking at it) and it shouldn't affect the other
> functionality, so why not commit it..
>
> Cheers
> D.
Søren Hauberg wrote:
>>I would be willing to integrate it into octave-forge if someone can
>>give me SVN access etc.
>
> I'll need your sourceforg
Obsessive MathsFreak wrote:
>> Ok, I just download the same version of the package as you and ran the
>> same command on the same version of octave, with the same messages..
>> However, there was no error and the package installed correctly.
>> Confirmed by running "pkg list".. I therefore beli
Obsessive MathsFreak wrote:
> On Tue, Mar 18, 2008 at 5:05 PM, David Bateman
> <[EMAIL PROTECTED]> wrote:
>
>> All octave-forge packages have a top-level configure file like
>>
>> if [ -e src/configure ]; then
>> cd src
>> ./configure $*
>> fi
>>
>> Note the test for the existence of the
On Tue, Mar 18, 2008 at 5:05 PM, David Bateman
<[EMAIL PROTECTED]> wrote:
> All octave-forge packages have a top-level configure file like
>
> if [ -e src/configure ]; then
> cd src
> ./configure $*
> fi
>
> Note the test for the existence of the src/configure before proceeding.
> If this
Obsessive MathsFreak wrote:
> On Tue, Mar 18, 2008 at 4:48 PM, Søren Hauberg <[EMAIL PROTECTED]> wrote:
>
>> tir, 18 03 2008 kl. 16:36 +, skrev Obsessive MathsFreak:
>>
>>
>>> The latest octave-forge integration package (1.0.4) will not install.
>>>
>> It installs fine on my ma
On Tue, Mar 18, 2008 at 4:48 PM, Søren Hauberg <[EMAIL PROTECTED]> wrote:
>
> tir, 18 03 2008 kl. 16:36 +, skrev Obsessive MathsFreak:
>
> > The latest octave-forge integration package (1.0.4) will not install.
> It installs fine on my machine. What version of Octave are you using,
> and how
tir, 18 03 2008 kl. 16:36 +, skrev Obsessive MathsFreak:
> The latest octave-forge integration package (1.0.4) will not install.
It installs fine on my machine. What version of Octave are you using,
and how did you try to install the package?
> There is no source directory in the tarball.
I d
Obsessive MathsFreak wrote:
> The latest octave-forge integration package (1.0.4) will not install.
>
> There is no source directory in the tarball.
>
>
There isn't an src/ directory in the integration package in the SVN
either.. So that is not an issue. What do you mean by "will not
install"? W
The latest octave-forge integration package (1.0.4) will not install.
There is no source directory in the tarball.
--
May The Maths Be With You
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R
13 matches
Mail list logo
