Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#15302 closed enhancement (fixed)

Update misc. optional spkgs to the new directory layout

Reported by: Volker Braun Owned by:
Priority: major Milestone: sage-6.0
Component: packages: optional Keywords:
Cc: Harald Schilly Merged in:
Authors: Volker Braun Reviewers: R. Andrew Ohana
Report Upstream: N/A Work issues:
Branch: u/vbraun/optional_packages (Commits, GitHub, GitLab) Commit: 6f4e944b9530418f326661f2cf811fe046f4ad25
Dependencies: Stopgaps:

Status badges

Change History (15)

comment:1 Changed 9 years ago by Volker Braun

Branch: u/vbraun/optional_packages
Commit: 1d3da2b304921680b32d76f1cac05d88b5de95d5

New commits:

[changeset:1d3da2b]add fixed openssl
[changeset:2b97b74]updated libogg and libtheora, fixed sage-git layout

comment:2 Changed 9 years ago by Volker Braun

TODO: investigate PyQt_x11, TOPCOM, valgrind

comment:3 Changed 9 years ago by Volker Braun

Description: modified (diff)

comment:4 Changed 9 years ago by Volker Braun

Component: buildpackages: optional

comment:5 Changed 9 years ago by Volker Braun

Valgrind has already been fixed in #13060.

comment:6 Changed 9 years ago by Volker Braun

PyQt_x11 also works, just needs the dependency optional sip.spkg first.

comment:7 Changed 9 years ago by git

Commit: 1d3da2b304921680b32d76f1cac05d88b5de95d56f4e944b9530418f326661f2cf811fe046f4ad25

Branch pushed to git repo; I updated commit sha1. New commits:

[changeset:6f4e944]added the topcom optional spkg

comment:8 Changed 9 years ago by Volker Braun

Description: modified (diff)
Status: newneeds_review

comment:9 Changed 9 years ago by R. Andrew Ohana

Milestone: sage-5.13sage-6.0

comment:10 Changed 9 years ago by R. Andrew Ohana

Reviewers: R. Andrew Ohana
Status: needs_reviewpositive_review

Seems fine to me.

comment:11 Changed 9 years ago by Volker Braun

Cc: Harald Schilly added

Harald, please mirror the new tarball.

comment:12 Changed 9 years ago by Volker Braun

Status: positive_reviewclosed

comment:13 Changed 9 years ago by Volker Braun

Resolution: fixed

comment:14 Changed 9 years ago by Harald Schilly

I've put them into the optional directory, but I doubt that's correct. Should they be in the corresponding upstream directories? (And create a new directory there, if it doesn't exist?)

I'm also wondering about having different versions there, as it is right now in many of these directories.

(Sorry about my questions, but I don't know about the mechanics behind these new directories.)

comment:15 in reply to:  14 Changed 9 years ago by R. Andrew Ohana

Replying to schilly:

Should they be in the corresponding upstream directories? (And create a new directory there, if it doesn't exist?)

This is correct (I've just done this for these packages).

I'm also wondering about having different versions there, as it is right now in many of these directories.

We already are hosting multiple versions of standard packages (e.g. r, pari), and I see no reason why we couldn't host multiple versions of optional packages either.

Note: See TracTickets for help on using tickets.