On 2015-09-10, John Cremona <john.crem...@gmail.com> wrote: > Am I right that Simon's package is one (perhaps the only one) for which (B) > would be useful? If that is true then I don't wish to make things hard for > Simon. But then I don't know what the obstacles are to converting his spkg.
Partially my ignorance. Partially the fact that the code is divided into three parts. The first has a proper upstream (MeatAxe), but we use a very old version (that said, even the latest version is several years old, and does not appear to be faster, but has almost all function names changed). The other two parts are not published elsewhere, and somehow it seems odd to me to artificially create an upstream repository, as the spkg *IS* the upstream repository (but perhaps I am the only one who finds it odd...). Anyway, it currently looks like the spkg will be converted to a new-style package. Something else: Of course each package has a maintainer resp. an upstream contact. Can this information be automatically extracted? Then, if an error occurs during installation, for whatever reason, the error message could clearly state: "Please contact f...@bar.com about the problem." If I recall correctly, the current error messages only mention sage-devel. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
