Added 'linux' entry

.gitignore

@@ -0,0 +1,18 @@
+# ---> Racket
+# gitignore template for the Racket language
+# website: http://www.racket-lang.org/
+
+# DrRacket autosave files
+*.rkt~
+*.rkt.bak
+\#*.rkt#
+\#*.rkt#*#
+
+# Compiled racket bytecode
+compiled/
+*.zo
+
+# Dependency tracking files
+*.dep
+
+*.bak

LICENSE

@@ -0,0 +1,117 @@
+GNU GENERAL PUBLIC LICENSE
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
+
+Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
+
+Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
+
+     a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
+
+     b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
+
+     c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
+
+     a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+
+     b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+
+     c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
+
+If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
+
+5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
+
+7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     one line to give the program's name and an idea of what it does. Copyright (C) yyyy name of author
+
+     This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+     You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
+
+     Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
+
+     Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice

Makefile.rkt

@@ -0,0 +1,46 @@
+#lang racket-makefile
+
+(require git
+         package-zipper)
+
+(target all
+        (displayln "main branch: use (make clean) or (make package)"))
+
+(target clean
+        (for-each (λ (f) (displayln f) (rm-f f)) (list-files "." #px"([.]bak|~)$" #:recursive #t))
+        (for-each (λ (d) (displayln d) (rm-rf d)) (list-dirs "." #px"(compiled|doc)$" #:recursive #t))
+        (when (directory-exists? "scrbl")
+          (for-each (λ (f) (displayln f) (rm-f f)) (list-files "scrbl" #px"[.](css|js|html)$")))
+        )
+
+(target package
+        (deps clean)
+        (zip-package))
+
+(target housekeeping
+        (displayln "Committing changes for:")
+        (let ((changes (git 'status)))
+          (when (> (length changes) 0)
+            (dgit 'status)
+            (displayln "Adding...")
+            (dgit 'add '-A)
+            (displayln "Committing...")
+            (dgit 'commit (git-prompt))
+            (displayln "Pushing...")
+            (dgit 'push)))
+        )
+
+(target windows
+        (deps housekeeping)
+        (displayln "Switching to x86_64-win32")
+        (dgit 'switch "x86_64-win32"))
+
+(target linux-x86_64
+        (deps housekeeping)
+        (displayln "Switching to x86_64-linux")
+        (dgit 'switch "x86_64-linux"))
+
+(target linux
+        (deps linux-x86_64))
+
+

README.md

@@ -1,11 +1,437 @@
 # racket-audio-native-libs
 
-Meta-package for the native libraries used by `racket-audio`.
+Native library distribution repository for `racket-audio`.
 
-This branch contains no native libraries. It selects the package matching the
+This repository contains the platform-specific native libraries used by
-current Racket platform:
+`racket-audio`. It uses one Git branch per published Racket package.
 
-    Windows x86_64     racket-audio-x86_64-win32
+The `main` branch contains the build and maintenance files. The other branches
-    Linux x86_64       racket-audio-x86_64-linux
+contain the actual Racket packages that are registered in the Racket Package
-    Linux ARM64        racket-audio-aarch64-linux
+Index.
-    macOS Apple Silicon racket-audio-aarch64-macosx
+
+## Branch structure
+
+The repository uses the following branches:
+
+```text
+main
+native-libs
+x86_64-win32
+x86_64-linux
+aarch64-linux
+aarch64-macosx
+```
+
+Their purpose is:
+
+```text
+main
+    Build scripts, documentation and maintenance files.
+
+native-libs
+    Meta-package: racket-audio-native-libs.
+    Selects the correct platform package.
+
+x86_64-win32
+    Native libraries for 64-bit Windows.
+
+x86_64-linux
+    Native libraries for 64-bit Intel/AMD Linux.
+
+aarch64-linux
+    Native libraries for 64-bit ARM Linux, for example a 64-bit Raspberry Pi.
+
+aarch64-macosx
+    Native libraries for Apple Silicon macOS, for example an M1 Mac.
+```
+
+Each platform branch is a separate Racket package.
+
+## Package names
+
+The intended Racket package names are:
+
+```text
+racket-audio-native-libs
+racket-audio-x86_64-win32
+racket-audio-x86_64-linux
+racket-audio-aarch64-linux
+racket-audio-aarch64-macosx
+```
+
+`racket-audio` itself should depend on:
+
+```text
+racket-audio-native-libs
+```
+
+The `racket-audio-native-libs` package then selects the correct platform
+package.
+
+This keeps the Racket code in `racket-audio` independent of the operating
+system and architecture.
+
+## Native package layout
+
+A platform branch contains the native libraries directly in the root of the
+branch, together with `info.rkt`.
+
+For example, the `x86_64-win32` branch may look like:
+
+```text
+info.rkt
+portaudio.dll
+libsndfile-1.dll
+libmpg123-0.dll
+...
+```
+
+The exact DLL names depend on the libraries used by `racket-audio`.
+
+The corresponding `info.rkt` uses `copy-foreign-libs`:
+
+```racket
+#lang info
+
+(define collection 'multi)
+
+(define version "0.1.0")
+
+(define pkg-desc
+  "native libraries for \"racket-audio\" on \"x86_64-win32\"")
+
+(define pkg-authors
+  '(hans))
+
+(define install-platform
+  "win32\\x86_64")
+
+(define copy-foreign-libs
+  '("portaudio.dll"
+    "libsndfile-1.dll"))
+
+(define deps
+  '("base"))
+```
+
+Every native library that must be installed with the package must be listed in
+`copy-foreign-libs`.
+
+This also includes DLLs, shared objects or dylibs that are runtime dependencies
+of the primary audio libraries.
+
+During package setup, Racket copies these files to a location that can be found
+by `ffi-lib`.
+
+## Meta-package
+
+The `native-libs` branch contains the package:
+
+```text
+racket-audio-native-libs
+```
+
+It contains no native libraries itself.
+
+Its `info.rkt` selects the correct package based on the current Racket
+platform.
+
+Conceptually:
+
+```text
+racket-audio
+    |
+    +-- racket-audio-native-libs
+            |
+            +-- racket-audio-x86_64-win32
+            +-- racket-audio-x86_64-linux
+            +-- racket-audio-aarch64-linux
+            +-- racket-audio-aarch64-macosx
+```
+
+Only the package matching the current platform is installed.
+
+## Use from racket-audio
+
+The `racket-audio` package should declare `racket-audio-native-libs` as a
+dependency in its `info.rkt`.
+
+For example:
+
+```racket
+(define deps
+  '("base"
+    "racket-audio-native-libs"))
+```
+
+The FFI code should preferably load libraries by their logical name instead of
+using machine-specific absolute paths.
+
+For example:
+
+```racket
+(ffi-lib "portaudio")
+```
+
+rather than:
+
+```racket
+(ffi-lib "C:\\some\\local\\directory\\portaudio.dll")
+```
+
+The native package is responsible for installing the actual library for the
+current platform.
+
+## Development workflow
+
+Development and package preparation take place on `main`.
+
+The platform branches should contain only the files required for the published
+Racket package.
+
+A typical Windows workflow is:
+
+```text
+main
+    |
+    | prepare/test Windows DLL package
+    v
+x86_64-win32
+    |
+    | commit + push
+    v
+Racket Package Index
+```
+
+The same approach can later be used for Linux, Raspberry Pi and macOS.
+
+## Adding or updating a Windows package
+
+Start on `main`:
+
+```bash
+git switch main
+git pull
+```
+
+Prepare or collect the required 64-bit Windows DLL files.
+
+Before publishing, verify that all runtime dependencies are included.
+
+Then switch to the platform branch:
+
+```bash
+git switch x86_64-win32
+```
+
+Update:
+
+```text
+info.rkt
+*.dll
+```
+
+Make sure `copy-foreign-libs` contains every DLL that belongs to the package.
+
+Commit and push:
+
+```bash
+git add info.rkt *.dll
+git commit -m "Update Windows native libraries"
+git push
+```
+
+## Adding or updating Linux x86_64
+
+Use:
+
+```bash
+git switch x86_64-linux
+```
+
+The branch will normally contain:
+
+```text
+info.rkt
+*.so
+*.so.*
+```
+
+Include all shared libraries required at runtime.
+
+After testing:
+
+```bash
+git add .
+git commit -m "Update Linux x86_64 native libraries"
+git push
+```
+
+## Adding or updating Raspberry Pi / Linux ARM64
+
+For a Raspberry Pi running a 64-bit operating system and 64-bit Racket, use:
+
+```bash
+git switch aarch64-linux
+```
+
+This package is intended for:
+
+```text
+aarch64-linux
+```
+
+Build the libraries natively on the Raspberry Pi where practical.
+
+After testing:
+
+```bash
+git add .
+git commit -m "Update Linux ARM64 native libraries"
+git push
+```
+
+## Adding or updating Apple Silicon macOS
+
+For an Apple Silicon Mac, such as an M1 Mac, use:
+
+```bash
+git switch aarch64-macosx
+```
+
+The branch normally contains:
+
+```text
+info.rkt
+*.dylib
+```
+
+Build and test the libraries on the Apple Silicon target machine.
+
+After testing:
+
+```bash
+git add .
+git commit -m "Update Apple Silicon native libraries"
+git push
+```
+
+## Testing a platform package locally
+
+Before registering or updating a package in the Racket Package Index, install
+the platform branch locally and verify that `racket-audio` can load and use the
+libraries.
+
+For example, from a checkout of the platform branch:
+
+```bash
+raco pkg install --auto .
+```
+
+After changing an already installed package, use the normal Racket package
+update/reinstall workflow as appropriate.
+
+The important test is that the existing FFI code can load the libraries without
+using local absolute paths.
+
+## Racket Package Index
+
+Each published branch is registered as a separate Racket package.
+
+The source URL can point directly to the corresponding Git branch.
+
+Conceptually:
+
+```text
+racket-audio-native-libs
+    <repository-url>#native-libs
+
+racket-audio-x86_64-win32
+    <repository-url>#x86_64-win32
+
+racket-audio-x86_64-linux
+    <repository-url>#x86_64-linux
+
+racket-audio-aarch64-linux
+    <repository-url>#aarch64-linux
+
+racket-audio-aarch64-macosx
+    <repository-url>#aarch64-macosx
+```
+
+The Racket Package Index therefore does not need a separate manually uploaded
+ZIP file. The Git branch itself is the package source.
+
+## Initial branch publication
+
+If the branches exist locally but not yet on `origin`, publish them with:
+
+```bash
+git push -u origin native-libs
+git push -u origin x86_64-win32
+git push -u origin x86_64-linux
+git push -u origin aarch64-linux
+git push -u origin aarch64-macosx
+```
+
+After that, a normal:
+
+```bash
+git push
+```
+
+is sufficient when working on a branch that has its upstream configured.
+
+## Build automation
+
+The first goal is to make the packaging work reliably using already available
+native libraries.
+
+After that, `main` can grow into a build orchestrator using Racket itself.
+
+The intended direction is:
+
+```text
+Windows machine
+    -> build x86_64-win32
+
+Linux x86_64 machine
+    -> build x86_64-linux
+
+Raspberry Pi 64-bit
+    -> build aarch64-linux
+
+Apple Silicon Mac
+    -> build aarch64-macosx
+```
+
+The build orchestration can use `racket-makefile`, the Racket `git` module and,
+for remote targets, SSH or another small remote-execution layer.
+
+The native libraries should preferably be built on the target architecture
+instead of cross-compiled, unless there is a good reason to do otherwise.
+
+## Versioning
+
+The version in each platform package should correspond to the native library
+set delivered by that branch.
+
+When changing the packaged native libraries, update the package version where
+appropriate and keep the meta-package dependency versions compatible.
+
+## Licenses
+
+Native libraries may have licenses that differ from the license of the Racket
+wrapper.
+
+Before publishing a new library or version, verify:
+
+```text
+- the upstream license;
+- whether binary redistribution is permitted;
+- whether license or copyright files must be included;
+- whether additional runtime libraries have separate license requirements.
+```
+
+Do not assume that the license of `racket-audio` automatically covers the
+native binaries.

info.rkt

@@ -1,31 +0,0 @@
-#lang info
-
-(define collection 'multi)
-
-(define version "0.1.0")
-
-(define pkg-desc
-  "native libraries for \"racket-audio\"")
-
-(define pkg-authors
-  '(hans))
-
-(define license
-  '(Apache-2.0 OR MIT))
-
-(define deps
-  '("base"
-    ["racket-audio-x86_64-win32"
-     #:platform "win32\\x86_64"]
-    ["racket-audio-x86_64-linux"
-     #:platform "x86_64-linux"]
-    ["racket-audio-aarch64-linux"
-     #:platform "aarch64-linux"]
-    ["racket-audio-aarch64-macosx"
-     #:platform "aarch64-macosx"]))
-
-(define update-implies
-  '("racket-audio-x86_64-win32"
-    "racket-audio-x86_64-linux"
-    "racket-audio-aarch64-linux"
-    "racket-audio-aarch64-macosx"))