Re: [Octave Forge] Octave 4.0 call for packages

[Tatsuro MATSUOKA]

----- Original Message -----

> From: c. 
> To: Tatsuro MATSUOKA 
> Cc: Carnë Draug ; Sebastian Schöps ; Jacopo Corno ; octave-maintainers
> Date: 2015/4/9, Thu 01:47
> Subject: Re: [Octave Forge] Octave 4.0 call for packages
> 
> 
> On 8 Apr 2015, at 15:56, Tatsuro MATSUOKA <address@hidden> wrote:
> 
>>  --- Jacopo Corno < wrote:
>>>  Il 07/04/2015 20:12, Carlo de Falco ha
>>>       scritto:
>>> 
>>>  odepkg does have a maintener but its development
>>>         moved out of sf into a separate repo.
>>>  Jacopo can you comment on the status of odepkg in general and
>>>         odepkg in particular?
>>>  c.
>>> 
>>> 
>>>  The repository Carlo is mentioning is
>>> 
>>>  https://bitbucket.org/robs88/octave-odepkg
>>> 
>>>  The structure that was used in odepkg-0.8.4 was changed two years
>>>     ago for SoCiS together with the introduction of geometric
>>>     integrators. Some more info on the current version is here
>>>     (http://geointegratorssocis.blogspot.de/)
>>> 
>>>  More recently I cleaned up the code and modified it to allow all
>>>     Matlab options to be used at least for the most commonly used
>>>     solvers like ode45. The plan is to push these solvers to the core,
>>>     but I still have to take care of adding those to the tracker.
>>> 
>>>  Best,
>>>  Jacopo
>>> 
>>> 
>>>  Il 07/apr/2015 13:21 "Carnë Draug" 
>>>         ha scritto:
>>>  On 7 April
>>>           2015 at 11:30, tmacchant  wrote:
>>>>  [...]
>>>>  Now control and image packages work on 4.0. Right?
>>> 
>>>  Yes.
>>> 
>>>>  I use the odepkg package in order to run Matlab code as
>>>           it is.
>>>>  (ode45)
>>>> 
>>>>  If  odepkg does not work on 4.0, I have to write rapper
>>>           to lsode or the code
>>>>  is modified to use lsode instead.
>>>> 
>>>>  Does anyone know of the state of the odepkg package?
>>> 
>>>  The version on the repositories should work on 4.0.0.  But the
>>>           package does
>>>  not have a maintainer that will clean it up and make a
>>>           release.  So you could
>>>  use it but you'll have to prepare the package yourself.
>>> 
>>>  Carnë
>>> 
>>  I am very glad to hear that odepkg functions are revised on the sparated 
> project.  However, if the support of the odepkg package is stopped at 4.0.0 
> release, many people will be disappointed.
>> 
>>  The odepkg package on the mercurial repository can be compiled on octave 
> 4.0.0-rc2 with small patch to src/Makefile by JohnD.
>> 
>>  Please allow me to push the temporal release of the odepkg package on the 
> current mercurial repository for upcoming octave release of 4.0.0.
>> 
>>  http://savannah.gnu.org/bugs/?44769
>> 
>>  Tatsuro
> 
> 
> Tatsuro,
> 
> The new repository is NOT a separate project, 
> that is just the current development version 
> of the package, the one on sourceforge has not
> been yet updated to include latest changes.
> 
> This is, to my understanding, the new trend in 
> Forge packages, development happens elsewhere then
> the repository is updated just before the release.
> 
> The sourceforge repository was not updated because
> no release was made yet. I believe it would anyway
> make more sense to synchronize the two repos now to 
> avoid more confusion, so if you want to merge the
> changes on bitbucket to sourceforge, please go ahead.
> 
> BTW do the changes made to allow compatibility with
> 4.0 break 3.8 compatibility?
> 
> Many people (e.g. Mac users) will be stuck with Octave 3.8
> for a while, so if 
> 
> pkg install -forge odepkg 
> 
> will not work for them that may be a problem...
> 
> c.



> The new repository is NOT a separate project, 
> that is just the current development version 
> of the package, the one on sourceforge has not
> been yet updated to include latest changes.


I understand.

> BTW do the changes made to allow compatibility with
> 4.0 break 3.8 compatibility?

> Many people (e.g. Mac users) will be stuck with Octave 3.8
> for a while, so if 
> 
> pkg install -forge odepkg 
> 
> will not work for them that may be a problem...


I have confirmed the 3.8 compatibility in current mercurial repository source 
on ubuntu 14.04 (32 and 64 bit) and window 7 (32 bit).


> The sourceforge repository was not updated because
> no release was made yet. I believe it would anyway
> make more sense to synchronize the two repos now to 
> avoid more confusion, so if you want to merge the
> changes on bitbucket to sourceforge, please go ahead.


Hmmm. 

I do not have plan to do so.
What is important is now that peoples can use odepkg package on upcoming 
release ver. 4.0.0.

I will switch my intention to make the patched tar-ball of the odepkg-0.8.4 
(e.g. octave-0.8.4_oct4.tar.gz) but not odepkg-0.8.5. The patched tar-ball will 
be uploaded my personal web site and I announce it on octave-mailing list.

Tatsuro