Opened 6 years ago

Closed 3 years ago

Last modified 2 years ago

#21538 closed enhancement (wontfix)

./configure --with-packages=...

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build: configure Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by mkoeppe)

./configure should accept an argument --with-packages=... so that a user can request a list of packages to be installed.

One could consider to have sage -i edit config.status (ac_cs_config) whenever a package is installed.

Also there should be an argument --ignored-installed-packages so that the contents of $SAGE_LOCAL/var/lib/sage/installed is ignored by configure. This is may be useful to ensure predictable builds.

See also: #21700 - crucial to get all dependencies of all optional packages right, because we no longer can tell the user to "first install this, then install that".

Change History (9)

comment:1 Changed 6 years ago by mkoeppe

  • Description modified (diff)

comment:2 Changed 6 years ago by mmezzarobba

Why not an argument --enable-foo (and/or perhaps --with-foo=/path/where/installed, depending on the answer to for each package foo?

comment:3 Changed 6 years ago by mkoeppe

Yes, this syntax could also work and is probably a better idea.

I like --with-foo=/path/where/installed too, but as I said on #21566, it won't happen on this ticket.

comment:4 Changed 6 years ago by mkoeppe

  • Description modified (diff)

comment:5 Changed 3 years ago by embray

  • Milestone sage-7.4 deleted

comment:6 Changed 3 years ago by embray

#27567 offers a slightly different approach, but I think effectively serves the same purpose as this proposal.

One thing it doesn't do yet is provide a way to enable specific optional/experimental packages at configure time. One might also consider that useful, but I'm treating it as a separate issue for now.

comment:7 Changed 3 years ago by embray

  • Milestone set to sage-duplicate/invalid/wontfix
  • Resolution set to wontfix
  • Status changed from new to closed

Superseded for now by #27567, though some of the suggestions in this ticket like --ignore-installed-packages might be useful down the line.

comment:8 Changed 3 years ago by mkoeppe

Not quite - what's missing is the possibility to add optional packages in the configure call.

comment:9 Changed 2 years ago by mkoeppe

This was implemented in #28095 (Add --enable-OPTIONALSPKG options to configure).

Note: See TracTickets for help on using tickets.