
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Describe the problem
It is a common practice for boards platforms to contain platform bundled libraries that are a variant of a common library distributed via Library Manager, modified to be compatible with the architecture of the boards platform (example).
arduino-cli lib list
does not list the platform bundled library when the library of the same name is installed globally (e.g. indirectories.user
).To reproduce
Because the LIBRARY_LOCATION_USER installed version of "USBHost" is specified for
sam
architecture, it is reasonable that it not be shown inarduino-cli lib list --fqbn arduino:samd:mkrzero
output (because that board issamd
architecture), but the version of the library bundled with thearduino:samd
platform should be shown.Expected behavior
arduino-cli lib list --all --fqbn
should always list all installed libraries matching the search query.Arduino CLI version
nightly-20211112 Commit: bf4a784
Operating system
Windows
Operating system version
10
Additional context
The compilation process correctly discovers the platform bundled library even though it was not shown in the
lib-list --fqnb
output:Even though it results in the example above exhibiting the most dramatic form of the bug's manifestation, the bug is not dependent on an architecture mismatch of the Library Manager lib, as the demonstration below shows.
In the following demonstration, the globally installed library is shown in the
lib list
output because it is compatible with the board'smbed_portenta
architecture, but the platform bundled library is incorrectly not shown in the output, just as in the previous demonstration.arduino-cli lib list --all --fqbn
could be a very useful tool for investigating library dependency resolution outcomes, which are regularly a source of confusion for platform and library developers and users when a different library from the one they expected is selected. But, with this bug, it would end up only contributing more confusion since the library that will be selected by the build system is not even shown in thelib list
output.Issue checklist
The text was updated successfully, but these errors were encountered: