[MacPorts] #41007: textmate2: add missing Mavericks build dependency on gnutar

[MacPorts]

#41007: textmate2: add missing Mavericks build dependency on gnutar
------------------------+-----------------------
  Reporter:  aronnax@…  |      Owner:  cal@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.2.0
Resolution:             |   Keywords:  mavericks
      Port:  textmate2  |
------------------------+-----------------------

Comment (by aronnax@…):

 Replying to [comment:9 ryandesign@…]:
 > Replying to [comment:8 pjkim00@…]:
 > > If reinstalling macports as described above installs gnutar and it
 builds correctly, then no problem.
 >
 > It does not. Building MacPorts causes it to determine what tar command
 is available. On previous versions of OS X, it determined that `gnutar`
 was available, and used it. On Mavericks, it will determine that `tar` is
 available and use it. The problem described in MavericksProblems is when
 you build MacPorts on an earlier OS and then try to use it on Mavericks.
 Don't do that.

 I didn't build MacPorts; I am using the Mavericks dmg.

 >
 > > The only scenario I can understand is if textmate2 actually does not
 need gnutar but explicitly lists it as a dependency. Is that the case?
 >
 > textmate2 does not list a dependency on gnutar. But the file
 bin/create_default_bundles_tbz in the textmate2 source code runs the
 command `gnutar -cf "$TBZ_DST~" "$BZIP2_FLAG" -C "$BUNDLES_DST" "Managed"`
 which of course fails if `gnutar` does not exist. I don't see any gnutar-
 specific flags in use there, so I surmise that using `tar` instead of
 `gnutar` in that script would work fine. And yes, as suggested earlier in
 this thread, that should be reported to the developer of textmate2 so that
 he can make that change.
 >
 > > It seems that a LOT of ports require gnutar so I don't think that
 removing gnutar from just the textmate2 build script will do much for the
 overall macports experience.
 >
 > Assuming that MacPorts has been built on the OS it is being used on,
 then:
 >  * Any port that declares a dependency on gnutar is fine.
 >  * Any port that doesn't declare a dependency on gnutar and doesn't need
 gnutar is fine.
 >  * Any port that uses `tar` is fine.
 >  * The problem is only ports that use gnutar but don't declare a
 dependency on it, like textmate2. That's what this ticket is about.

 Correct.

-- 
Ticket URL: <https://trac.macports.org/ticket/41007#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X