[MacPorts] #54459: libtool: installs files with extended attribute com.dropbox.attributes

[MacPorts]

#54459: libtool: installs files with extended attribute com.dropbox.attributes
-------------------------+---------------------
 Reporter:  raimue       |      Owner:  larryv
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:               |       Port:  libtool
-------------------------+---------------------
 Apparently, upstream shipped the libtool-2.4.6 distfile tarball with
 extended attributes on the source files. These will be retained when
 installing.

 {{{
 $ $ ls -la@ $(port work libtool)/libtool-2.4.6/m4/libtool.m4
 -rw-r--r--@ 1 macports  admin  305723 Jan 20  2015
 /opt/local/var/macports/build/_Users_raimue_src_macports_ports_devel_libtool/libtool/work/libtool-2.4.6/m4/libtool.m4
         com.dropbox.attributes      83
 $ ls -la@ /opt/local/share/aclocal/libtool.m4
 -rw-r--r--@ 1 root  admin  305723 Jun 24 14:17
 /opt/local/share/aclocal/libtool.m4
         com.dropbox.attributes      83
 }}}

 Normally, these would not cause a problem. However, as build scripts copy
 files like `libtool.m4` to local build directories, they are likely to end
 up in other distribution tarballs. This issue only exists on macOS, as on
 other platforms these extended attributes would just be visible as `._*`
 files, which are ignored and not processed in any way.

 Upstream bug report: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20293

 I am aware the release more than two years old, but maybe it's not too
 late to do something about it.
 I think we should remove these extended attributes when installing libtool
 as they are unnecessary clutter.

--
Ticket URL: <https://trac.macports.org/ticket/54459>
MacPorts <https://www.macports.org/>
Ports system for macOS