[MacPorts] #52992: fluid-soundfont, generaluser-soundfont: add new sound fonts

[MacPorts]

#52992: fluid-soundfont, generaluser-soundfont: add new sound fonts
----------------------------------------------------+--------------------
  Reporter:  mojca                                  |      Owner:  RJVB
      Type:  submission                             |     Status:  closed
  Priority:  Normal                                 |  Milestone:
 Component:  ports                                  |    Version:
Resolution:  fixed                                  |   Keywords:
      Port:  fluid-soundfont generaluser-soundfont  |
----------------------------------------------------+--------------------

Comment (by RJVB):

 Ah!

 I do *not* get those. Did you install a binary package from the build bots
 or one created locally?

 I think those ._ files might come from unzipping the original archive but
 what I don't understand is how the end up in the destroot. This is what's
 done during destroot:

 {{{
     xinstall -m 644 "${worksrcpath}/GeneralUser GS v${version}.sf2"
 ${dir}/GeneralUser_GS_v${version}.sf2

     set dir ${destroot}${prefix}/share/doc/${name}
     xinstall -m 755 -d ${dir}
     foreach f {CHANGELOG.txt LICENSE.txt README.txt "instrument
 lists/GU1.43 Percussion Map.pdf"} {
         xinstall -m 644 "${worksrcpath}/${f}" ${dir}
     }

     set dir ${destroot}${prefix}/share/examples/${name}
     xinstall -m 755 -d ${dir}
     xinstall -m 644 "${worksrcpath}/GUTest.mid" ${dir}
     foreach f [glob -nocomplain "${worksrcpath}/demo MIDIs/*"] {
         xinstall -m 644 "${f}" ${dir}
     }
 }}}

 Even if unzipping the archive creates those ._ files we shouldn't be
 copying them into the destroot.

 Mojca, is your ${workpath} on an HFS filesystem? You'd be seeing this kind
 of behaviour if you're using a FAT32 system, for instance.

--
Ticket URL: <https://trac.macports.org/ticket/52992#comment:25>
MacPorts <https://www.macports.org/>
Ports system for macOS