Re: [MacPorts] #52322: New port: depot_tools — a collection of tools for dealing with Chromium development

[MacPorts]

#52322: New port: depot_tools — a collection of tools for dealing with Chromium
development
--------------------------+--------------------------------
  Reporter:  william@…    |      Owner:  macports-tickets@…
      Type:  submission   |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.3.4
Resolution:               |   Keywords:
      Port:  depot_tools  |
--------------------------+--------------------------------

Comment (by william@…):

 OK, I've decided this is a Bad Idea. depot_tools seems frequently to try
 to add bits of itself when you run commands (gclient), and so having it
 installed in MacPorts' heirarchy is a no-go since this may (will) happen
 when a user (or another port being installed) uses those tools.

 Furthermore, as per https://www.chromium.org/developers/how-tos/get-the-
 code/working-with-release-branches , it does not seem to be possible,
 without access to the Google internal document called
 “go/ChromeReleaseBranches” (or equivalent internal knowledge of the build
 tools), to create a build tree containing a project which is managed by
 depot_tools and which matches a specific release tag of a product. Since
 my motivation for doing this was to get a build from source of the Dart
 SDK (Version 1.19.1 at the time of writing) from a specific release tag,
 in order to have a fixed version of the port available in MacPorts (as
 requested in #51751), there's no longer any purpose in this proposed
 depot_tools port, so please simply close this ticket! The only way this is
 likely to happen is if somebody at Google decides it's a good idea and
 provides a portfile encapsulating the secret knowledge regarding how to
 build a Dart SDK from a release tag, and the impression I have of that is
 that it's unlikely: for better or worse they have decided to make Dart a
 brew exclusive (as per https://plus.google.com/+dartlang/posts/WX47S62PjBs
 ). Of course, the brew installation just uses the prebuilt SDKs rather
 than building on the host Mac, as per https://github.com/dart-lang
 /homebrew-dart/blob/master/dart.rb …

-- 
Ticket URL: <https://trac.macports.org/ticket/52322#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS