Opened 15 months ago

Last modified 4 months ago

#29387 new defect

Complete solution for installing the generated *.pc files

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-9.4
Component: build Keywords:
Cc: dimpase, jhpalmieri Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: u/mkoeppe/system_blas_facade (Commits, GitHub, GitLab) Commit: b493a32df5c9bb08613e370759412e55a2501676
Dependencies: #29082, #29386 Stopgaps:

Status badges

Description

Follow up from #29082.

This ticket makes sure that installed pc files in SAGE_LOCAL are uninstalled correctly when the installation changes, via the staging/uninstalling mechanism extended to script packages by #29386.

  • Code in build/make/Makefile.in is removed in favor of creating one or several new type=script packages, whose spkg-install does the installation to SAGE_LOCAL.

Change History (5)

comment:1 Changed 15 months ago by mkoeppe

  • Branch set to u/mkoeppe/system_blas_facade

comment:2 Changed 15 months ago by mkoeppe

  • Commit set to b493a32df5c9bb08613e370759412e55a2501676
  • Dependencies set to #29082, #29386

The branch on the ticket is the old branch from #29082. Needs work.

Last 10 new commits:

​dbb9860build/pkgs/texlive/spkg-install: Fix up path
​8b1d5catrac 29287: rewording documentation
​057a66bMake pyopenssl a pip package
​8f6323esrc/sage/env.py: Fix up doctest on starting sage without SAGE_* variables
​0919086trac 29287: doc fixes
​6781790Move all BLAS PC file installation logic to new script package sage_sage_system_blas_facade
​30d3b82build/pkgs/openblas/spkg-configure.m4: Separate library names by spaces
​b68595eChange type
​7fd5e31fixup
​b493a32install sage_system_blas_facade

comment:3 Changed 14 months ago by mkoeppe

  • Milestone changed from sage-9.1 to sage-9.2

pushing these forward to 9.2

comment:4 Changed 10 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:5 Changed 4 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

Note: See TracTickets for help on using tickets.