#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 jhpalmieri):
Replying to [comment:6 leif]:
> Funny thing. I'd rather change the ''code'' to reflect the common
practice of using dashes in package names, i.e. taking the leftmost
substring that ''starts with a digit'' (and of course is preceded by a
hyphen) as the package version part.
>
> IMHO code that's unable to deal with dashes in package names is bad and
should be fixed, not the names. We shouldn't introduce or keep
restrictions that aren't really necessary, not only but especially if they
rule out what's widely used.
First of all, what's widely used ''in Sage'' is the convention here:
everything after the first hyphen is the version number. Look at the
names of the standard spkgs to see this.
Second, you might be right, but this is not the right place to discuss
design decisions like this: sage-devel is.
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. So it's not a big deal.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8679#comment:7>
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.
