Michael,

>> Thank you for working on this.

I thank you, too.

> I imagine many users are using octave-devel right now, not because they want 
> a development version, but because they want any version that works.

 I am one of them, but as a port maintainer-committer I know that
*-devel ports are unstable bleeding edge.

> I’m not sure I’d recommend adding a new octave-next port. That naming is 
> nonstandard. Instead, can’t we just wait awhile, then update octave-devel to 
> 3.7.x?

I agree with Ryan.

Takeshi
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to