Skip to content

Teach rustup/rustbuild about optional components #1006

Closed

Description

@brson

Today rustup knows about two types of packages: components (required), and extensions (optional, non-default). Some components though want to be installed by default, but optional (like docs).

To do this we have to change the manifest format in a backwards-compatible way. I suggest that we add a key "optional = true" to components that don't need to be installed. The build-manifest tool invoked by rustbuild needs to be modified to emit this key, and rustup needs to be taught to consume it.

Activity

  1. Diggsey commented on Mar 23, 2017

    @Diggsey
    Contributor

    I have a slight preference for doing the opposite (ie. flagging extensions as being "install-by-default") so that components are always required, and extensions are always optional. What do you think?

  2. brson commented on May 11, 2017

    @brson
    ContributorAuthor

    @Diggsey per discussion we decided to go with the original design, for backwards-compatibility concerns.

  3. brson commented on May 12, 2017

    @brson
    ContributorAuthor

    Once this feature exists, rustup-init also needs to be modified with a non-interactive commandline option to disable default components. If the interactive installer allows component selection (I don't recall) then that needs to be modified too, though it could be done as a followup.

  4. mikhail-m1 commented on May 16, 2017

    @mikhail-m1
    Contributor
  5. mikhail-m1 commented on May 18, 2017

    @mikhail-m1
    Contributor

    add optional to build-manifest tool mikhail-m1/rust@35a30af. Shell I do pull request to rust-lang/rust?

  6. mathstuf commented on Jul 25, 2019

    @mathstuf

    Ping? Any progress on this? I'd like to reduce the size of our multi-toolchain build images by nuking docs…

  7. kinnison commented on Jul 28, 2019

    @kinnison
    Contributor

    This work has been folded into the concept of installation profiles, which we're actively working on, though the over-all progress is slowed due to recent CI problems with Windows. You can follow the work in #1673

  8. mathstuf commented on Oct 25, 2019

    @mathstuf

    Now that profiles have landed, I think this can be closed.

  9. kinnison commented on Oct 25, 2019

    @kinnison
    Contributor

    I concur, thank you for the triage.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions