#8679: conventions for spkg names, rewriting sage-spkg
-----------------------------+----------------------------------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.4
Component: packages | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by leif):
Replying to [comment:7 jhpalmieri]:
> First of all, what's widely used ''in Sage'' is the convention here
Well, I didn't talk about common ''spkg'' names (of course they follow the
old rule).
Note that many spkgs are patched upstream packages, so their (original)
names won't necessarily follow ''Sage's'' naming convention; there are
indeed yet packages that had to be renamed.
> Second, you might be right, but this is not the right place to discuss
design decisions like this: sage-devel is.
The thread "ends" with a link to this ticket, whose description
(re-)states the convention, while the thread's title only mentions the
''mode'' package;
but never mind, I'll repost it there. ;-)
> Third, this is an issue which will only arise for developers -- people
producing new spkgs -- and they should be able to handle using hyphens or
underscores according to the conventions.
I think there's (with intent) no sharp line between Sage
developers/contributors/users; think of optional "third party" (s)pkgs.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8679#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
