On May 5, 7:16 am, simon.k...@uni-jena.de wrote:
> Hi Michael,
>
> > The whole point is that src contains clean upstream sources you can
> > download from wherever you document in SPKG.txt.
>
> OK. So what shall I do if most of the code is original, not from some
> "upstream"?
> In src/, I have
> - mtx2.2.3/, comprising *modified* MeatAxe 2.2.3
> - a folder with C-code by David Green, old but not yet published
> elsewhere
> - a folder with my own Cython stuff.
>
> So, I guess SPKG.txt should provide this information, mtx2.2.3 should
> comprise the *un*modified MeatAxe sources, and patches/ should provide
> the changes that I made to the MeatAxe sources? What must I do in
> order to ensure that the modifications given in patches/ will be
> automatically applied to the original sources, when the package is
> installed?
Well, given that this isn't going into the core of Sage I don't care
too much if src contains modified sources or not. We decided to
enforce the "clean upstream src" rule in Sage (and for many of the
currently maintained optional spkgs for example) since it is just
easier to update them, especially by people who did not create the
spkg in the first place.
In your case you have a somewhat odd mix of meataxe, C code and Cython
code, so I wouldn't worry about following the rules too much. Just
document things precisely in SPKG.txt to make it easier for someone
interested in working on your code.
> Best regards,
> Simon
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
