octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53695] tar.m and unpack.m are incompatible wi


From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #53695] tar.m and unpack.m are incompatible with BSD tar
Date: Sun, 24 Jun 2018 02:19:54 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Follow-up Comment #10, bug #53695 (project octave):

Would you consider as an alternative requiring a GNU tar, but doing a
configure-time check to locate it, and allowing a user override? As far as I
know, GNU tar is available on most systems, even if it has to be installed at
a non-default location or prefix (like `/usr/local/bin/gtar`), so it's not an
onerous requirement.

I'm working on a macOS installation of GNU Octave and running in to the same
problem, since the system-supplied tar on macOS is a BSD tar. It's easy to
install GNU Tar as a supplemental tar, but I'd need some way to point GNU
Octave at it.

A run time check might be even better, as long as there was a way to supply a
run time override that pointed Octave at the right GNU tar. That would make it
easier to package Octave for redistribution, to systems which may or may not
have GNU tar installed, and may have it installed at different locations.
Something like the `makeinfo_program` function that allows run time
specification of the texinfo location.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53695>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]