#21130: Cleaning fileserver.sagemath.org for optional packages
--------------------------------------+------------------------
       Reporter:  vdelecroix          |        Owner:
           Type:  task                |       Status:  new
       Priority:  major               |    Milestone:  sage-7.3
      Component:  packages: optional  |   Resolution:
       Keywords:                      |    Merged in:
        Authors:                      |    Reviewers:
Report Upstream:  N/A                 |  Work issues:
         Branch:                      |       Commit:
   Dependencies:                      |     Stopgaps:
--------------------------------------+------------------------

Comment (by leif):

 Replying to [ticket:21130 vdelecroix (ticket description)]:
 > See also #21130

 ???

 ----

 You (or we) shouldn't search for optional packages in `spkg/optional/`
 '''unless''' there's no new-style version of a package.

 All packages below `spkg/` are for "backwards-compatibility", i.e., older
 versions of Sage.

 At some point, all old-style packages should be converted, such that we
 can (in principle) disable the installation of legacy spkgs into newer
 versions of Sage.

 ----

 As you may know, I've always been against the "unified repo" as is (tying
 any spkg to specific Sage versions and vice versa, and offering only a
 single version of each at the same time), which is completely against the
 original philosophy (that anybody could offer ''his/her'' spkg, most being
 self-contained, some needing Sage library support of course).

 Because of this, it's difficult to generally disallow the installation of
 "old-style" spkgs, unless or until we have a new format and mechanism for
 truly "external" packages.  (I suggested to split spkgs into two parts,
 the '''S'''age '''pa'''ckage '''m'''etadata, `.spam`, and an upstream
 tarball, years ago.  We could still do the same for at least "external"
 packages, namely create/use a tarball with just what is now in
 `build/pkgs/<pkgname>/`, although a single plain text file à la Arch Linux
 or !Gentoo/Funtoo would be better.)

 A related problem is that our build / package system lacks any notion of
 version requirements, it always [en]forces to use exactly a single
 specific version of a package, no matter whether that's necessary or not,
 and true requirements are hardly documented.

--
Ticket URL: <https://trac.sagemath.org/ticket/21130#comment:6>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to