On Wed, Apr 21, 2010 at 8:55 AM, William Stein <[email protected]> wrote: > > > On Wed, Apr 21, 2010 at 8:49 AM, John H Palmieri <[email protected]> > wrote: >> >> According to our documentation, the "src" directory in an spkg should >> contain the "vanilla upstream code". I've seen a few spkg's that >> modify this by deleting stuff: >> >> - they might delete documentation (as long as it's not used in any >> way by Sage) >> - they might delete a Mercurial repository (as long as it's just the >> upstream repo, not the one that's supposed to be there) >> >> These changes make the spkg files much smaller, which is good. But >> are these acceptable changes? > > I think they should be, since they reduce bloat. I am for changing the > definition of src to be: > "src must be a subset of vanilla upstream code". > Absolutely nothing should be added, and sticking vanilla upstream there > shouldn't break the spkg.
For our hermes2d spkg package: http://hpfem.org/hermes2d/ I actually just added the "spkg-install" into the upstream git repository itself and the package is then just a tar bz2 archive of it (including the git repo). This works well for me, as it is super easy to install and maintain it. Would that be acceptable for Sage (I am not proposing to add it to sage, but I would like it to be compatible), or should the package look differently? Ondrej -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
