Opened 8 years ago
Last modified 8 years ago
#51751 new request
google dart language
| Reported by: | smittysauce (Chris Smith) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | Cc: | gallafent | |
| Port: |
Description
can we get support google dart language? this is currently supported by homebrew...
Change History (3)
comment:1 Changed 8 years ago by raimue (Rainer Müller)
comment:3 Changed 8 years ago by gallafent
The process for building a released version of the Dart SDK (as opposed to the current state of its development branch) is opaque. See #52322 for a bit more discussion of this, including the reference to the information which suggests looking at an internal Google document in order to find out how to build a project managed using the depot_tools, including its third party dependencies, from a release tag.
It's pretty straightforward to make a MacPort which simply installs the binary distribution as provided by the dart project, of course, as a big lump e.g. below /opt/local/libexec (for example, better suggestions welcome). Would this be of any use? The only advantage over installing by hand, then, is “automatic” updates. Clearly it doesn't fit well with the MacPorts philosophy of being able to build everything locally, but at this point it's hard to see an alternative without some help from a Google / Chromium internal person who knows the magic for building Dart SDK from a release tag, and there doesn't seem to be any inclination in that direction from the Dart team from what I can see!
The best way to get a new port into the official ports tree is to provide a Portfile. Please see the guide how Portfiles are written or look at existing ports for examples.