Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#15302 closed enhancement (fixed)

Update misc. optional spkgs to the new directory layout

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

Change History (15)

comment:1 Changed 6 years ago by vbraun

  • Branch set to u/vbraun/optional_packages
  • Commit set to 1d3da2b304921680b32d76f1cac05d88b5de95d5

New commits:

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

comment:2 Changed 6 years ago by vbraun

TODO: investigate PyQt_x11, TOPCOM, valgrind

comment:3 Changed 6 years ago by vbraun

  • Description modified (diff)

comment:4 Changed 6 years ago by vbraun

  • Component changed from build to packages: optional

comment:5 Changed 6 years ago by vbraun

Valgrind has already been fixed in #13060.

comment:6 Changed 6 years ago by vbraun

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

comment:7 Changed 6 years ago by git

  • Commit changed from 1d3da2b304921680b32d76f1cac05d88b5de95d5 to 6f4e944b9530418f326661f2cf811fe046f4ad25

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

[changeset:6f4e944]added the topcom optional spkg

comment:8 Changed 6 years ago by vbraun

  • Description modified (diff)
  • Status changed from new to needs_review

comment:9 Changed 6 years ago by ohanar

  • Milestone changed from sage-5.13 to sage-6.0

comment:10 Changed 6 years ago by ohanar

  • Reviewers set to R. Andrew Ohana
  • Status changed from needs_review to positive_review

Seems fine to me.

comment:11 Changed 6 years ago by vbraun

  • Cc schilly added

Harald, please mirror the new tarball.

comment:12 Changed 6 years ago by vbraun

  • Status changed from positive_review to closed

comment:13 Changed 6 years ago by vbraun

  • Resolution set to fixed

comment:14 follow-up: Changed 6 years ago by 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 6 years ago by ohanar

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.