octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[OF geometry] un-syncable with upstreeam


From: Juan Pablo Carbajal
Subject: [OF geometry] un-syncable with upstreeam
Date: Tue, 14 Aug 2018 00:00:02 +0200

Hi Phillip, Of leaders, and maintainers,

I was trying to release geometry today. It is impossible! (well very hard).
The problem is that from the beginning I made the mistake of trying to
convert the package to Octave and Of standards... wrong!

So I am inclined to:
1. Reduce the current geometry package to contain only our extensions to matgeom
2. Put 3rd party geometry code into matgeom package (which will just
package what comes from matgeom developers)
3. mapping will have to depend on geometry, which in turns depends on matgeom

Now the BIG issue with this:
The reason I tried to convert matgeom to octave standard was to be
able to include the package in OF. This is currently a nightmare!
So by making an Octave package matgeom that can be easily synched with
upstream, I will have to abandon Octave and OF standards and matgeom
wont be hosted in OF anymore cause it will be not compliant.
This means installation of packages that depend on matgeom wont be
automatic, e.g.
pkg install -forge geometry
will always fail due to missing dependency matgeom.

What to do in this scenario?

One alternative I see is to fork only what our extensions actually
need from matgeom and put those in geometry in a OF complaint form
(definitely diverging from matgeom). Beware! This is not minor amount
of functions, and to do it in a reasonable time I will need help.

Is this scenario better?

I will really appreciate your inputs here!

Regards,



reply via email to

[Prev in Thread] Current Thread [Next in Thread]