Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
redox
redox
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 211
    • Issues 211
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • redox-os
  • redoxredox
  • Issues
  • #913

Closed
Open
Opened Apr 09, 2017 by Jeremy Soller@jackpot51Owner

Is it really necessary to have rustc as a submodule?

Created by: ksf

The main issue is that its repository is a felt three gigabytes large and then pulls in llvm, which is another five terabytes.

At the same time, what redox needs from that repository (assuming a nighly rust is already available) is rather limited -- core, std, compiler-builtins, I think that's all.

Would it not be prudent to take the poke stick and prod the rustc people until they make those subdirectories submodules which redox can then use directly, without pulling in twenty exabytes of unnecessary code and history?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/redox#913