Minor portability issue: tar may not accept `xJf` flags: `tar: invalid option -- J`

[barracuda156]

@krlmlr This 9375cfa is not really portable, from what it looks:

--->  Building R-duckdb
xinstall: mkdir /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_R_R-duckdb/R-duckdb/work/build
Executing:  cd "/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_R_R-duckdb/R-duckdb/work/duckdb" && /opt/local/bin/R CMD INSTALL . --library=/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_R_R-duckdb/R-duckdb/work/build --install-tests 
* installing *source* package ‘duckdb’ ...
file ‘src/Makevars’ has the wrong MD5 checksum
** using staged installation
++ dirname ./configure
+ cd ./src
+ '[' -f '' ']'
+ cp include/to-tar.mk Makevars.duckdb
+ '[' -f duckdb.tar.xz ']'
+ tar xJf duckdb.tar.xz
tar: invalid option -- J
Try `tar --help' or `tar --usage' for more information.
ERROR: configuration failed for package ‘duckdb’

This is not a big deal, since patching this to use specifically gnutar fixes the issue, but perhaps worth at least either having a check or a note in README?

[krlmlr]

Thanks. I'll consider that if this is a widespread problem; recent tar on macOS and Linux seem to support this. For now, this issue might be documentation enough?

[barracuda156]

@krlmlr Yes, I think that is sufficient, perhaps. There should be no problem to build a modern gnutar on any platform, so in the worst case it is a matter of an extra dependency.

I added this now: https://github.com/macports/macports-ports/blob/d6c3003256410b8978c14c0a919c391dd3b2b307/R/R-duckdb/Portfile#L22-L26
(Easier just to depend on it that determine exact OS versions where that option is supported or not.)

[krlmlr]

Closed, we agreed to document and/or fix elsewhere.