Hello,
I had taken a quick look at the octave extension, and it seems that the main
issue is that most of them were not updated, as the installation way changed,
so that they were kept to old versions, still compatible with the installation
way provided in octave-1.0 port group.
For this reas
On 2013-5-25 16:08 , Blair Zajac wrote:
> On 5/24/13 5:12 AM, Michael Dickens wrote:
>> On Fri, May 24, 2013, at 03:42 AM, Aljaž Srebrnič wrote:
>>> Well, I can test them with octave-devel if you want!
>>
>> Give it a go!
>>
>> I picked 5 random octave-* ports (irsa, specfun, strings, ?don't
>> rem
On 5/24/13 5:12 AM, Michael Dickens wrote:
On Fri, May 24, 2013, at 03:42 AM, Aljaž Srebrnič wrote:
Well, I can test them with octave-devel if you want!
Give it a go!
I picked 5 random octave-* ports (irsa, specfun, strings, ?don't
remember?) and tried to install them (10.8.3 all latest); 4 i
On Fri, May 24, 2013, at 03:42 AM, Aljaž Srebrnič wrote:
> Well, I can test them with octave-devel if you want!
Give it a go!
I picked 5 random octave-* ports (irsa, specfun, strings, ?don't
remember?) and tried to install them (10.8.3 all latest); 4 installed.
Of those 4, I've figured out how to
I'd want to make sure that at least some (most?) of the octave-* ports
work. The octave-1.0 portgroup looks good, and should work for both
octave and octave-devel (any version) with respect to these ports. I
don't use the octave-* ports (yet), so I have no idea if they work or
not. If they do work
octave is at 3.2.4 while octave-devel is at 3.6.4. Any reason not to
copy octave-devel to octave and do work on octave until the next major
version of octave comes out?
Blair
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lis
