Generate and consume the package spec (.packages)

[sethladd]

This is the main tracking bug to implement the package spec proposal. This proposal has been accepted (but has not yet gone through TC52), and work has begun on implementing it.

This is the main tracking bug. Each platform's specific bug is below:

• VM: VM: Implementing the package spec proposal #23369
• VM: --packages doesn't deadlock: VM deadlocks when passed the "--packages" flag #23991
• dart2js: dart2js: Implementing the package spec proposal #23371, first released in 1.12.0-dev.0.0
• Analyzer: Analyzer: implementing package spec proposal (.packages) #23373
• Analysis Server: Analysis Server: implement support for .packages #23925
• Pub: global activate: write a .packages when globally installing a package pub#22
• Pub: merge new version into sdk: Merge the latest pub to dev #24094
• Pub: Pub: Implementing package spec proposal pub#16, first released in 1.12.0-dev.0.0
• Fix self-references in Pub: Self-references in generated .packages files point to the pubcache. pub#1294, will be released in 1.12.0-dev.3.0
• WebStorm: https://youtrack.jetbrains.com/issue/WEB-16466
• Fetching a .packages file after an http: entry point: Request: requesting a .packages file from http: import of an entry point #23952
• Test package_config on the packagebots Request: testing package_config on the packagebots #24092

Note that additional work will be needed in phase 2, see #24112

[sethladd]

Marked this as being blocked by #23373.

[sethladd]

Marked this as being blocked by #23374.

[sethladd]

Added Accepted label.

[sethladd]

See also this JetBrains plugin tracking issue: https://youtrack.jetbrains.com/issue/WEB-16466

[sethladd]

Added this to the 1.11 milestone.
Added Priority-High label.

[sethladd]

And we're accepted! dart-archive/dart_enhancement_proposals#5

[sethladd]

Added Started label.

[sigmundch]

Marked this as blocking #23565.

[sethladd]

dart2js has filed their merge request for this new functionality.

[nex3]

Since I don't see it linked anywhere here, the issue tracking the VM's implementation is #23369.

[sethladd]

Blocked by dart-lang/pub#1294

[nex3]

@sethladd When adding new sub-issues to meta-issues, it would be nice to include them in the master list as well (I've done so for this one).

[sethladd]

Sure. I didn't know if you wanted blockers that came up after we filed the meta issue, since they weren't original implementation issues.

[nex3]

I think the main function of the meta-issue is to give people a single place to see "what is the current status of X", so having everything in the main list is a good idea. I'll mention it in the wiki entry.

[sethladd]

sgtm!

[mit-mit]

Meta bug, assigning to self to drive to completion for 1.12.

[mit-mit]

Marking #23373 as complete in checlist

[mit-mit]

Moved #24093 to 1.13

[mit-mit]

Created a new issue #24112 to tracks the second phase for this feature targeted for 1.13. Deleting 1.13 work items from present issue that is bound to 1.12.

[mit-mit]

Marking testing task complete as #24092 was closed.

[mit-mit]

Marking this feature complete for 1.12. We will expand on this in 1.13, see #24112

[sethladd]

Note, there are many open issues around the implementation of this feature. A sample:

#24126
#24127
#24122
#24116