Re: OF: community packages depending on external packages?

[PhilipNienhuis]

Olaf Till-2 wrote
> Hi,
> 
> in recent package release submissions, the issue came up whether
> OF packages in the "community" category should be allowed to depend on
> packages in the "external" community.
> 
> I think not. The "community" category was meant for a tight connection
> with the development of core Octave. For this, our developer community
> was meant to have control over the "community" packages. This control
> is necessary, among others, for namespace issues.
> 
> "External" packages, on the other hand, are under the sole control of
> their individual maintainers. Sometimes, they indirectly depend on
> m-code developed only for Matlab.
> 
> If "community" packages depend on "external" packages, they depend on
> m-code which is not under the cotrol of our developer community. I
> think this would be a mistake.

What will happen now? is this discussion dropped / ignored?

Given that a new mapping package release is actually ready for a long long
time now (> 2 years) and it depends on new geometry and matgeom releases I'd
like to know what to do next.

If mapping is to become an external package, together with geometry and
matgeom, fine with me, then users can at least benefit from a new release.
Too bad for the concept of community packages then.

The way this process has been lingering on doesn't appear nice to me.

Philip




--
Sent from: https://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html