Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./configure --with-packages=... #21538

Closed
mkoeppe opened this issue Sep 19, 2016 · 8 comments
Closed

./configure --with-packages=... #21538

mkoeppe opened this issue Sep 19, 2016 · 8 comments

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented Sep 19, 2016

./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".

Component: build: configure

Issue created by migration from https://trac.sagemath.org/ticket/21538

@mkoeppe mkoeppe added this to the sage-7.4 milestone Sep 19, 2016
@mkoeppe

This comment has been minimized.

@mezzarobba
Copy link
Member

comment:2

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

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Sep 23, 2016

comment:3

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.

@mkoeppe

This comment has been minimized.

@embray embray removed this from the sage-7.4 milestone Mar 29, 2019
@embray
Copy link
Contributor

embray commented Mar 29, 2019

comment:6

#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.

@embray
Copy link
Contributor

embray commented May 9, 2019

comment:7

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

@mkoeppe
Copy link
Contributor Author

mkoeppe commented May 9, 2019

comment:8

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

@mkoeppe
Copy link
Contributor Author

mkoeppe commented May 1, 2020

comment:9

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants