# Installer virtuoso avec Homebrew, MacPorts, apt Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de virtuoso pour les workflows d'agents IA. ## installation ```sh sudo av install brew:virtuoso ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install virtuoso ``` Preuve: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install virtuoso ``` Preuve: MacPorts ports tree: devel/virtuoso/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - Debian apt (92%): ```sh sudo apt install python3-inifile ``` Preuve: Debian stable package indexes: python3-inifile from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz ## Faits du paquet - **Clé du paquet:** brew:virtuoso - **Gestionnaire de paquets:** Homebrew - **Version:** 7.2.17 - **Résumé source:** High-performance object-relational SQL database - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-05-12T11:10:35-04:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - inifile (alias) - isqlw (alias) - virt_mail (alias) - virtuoso-t (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 7.2.17 ## Historique du projet et usages Virtuoso, or Virtuoso Universal Server, is OpenLink Software's multi-model database and middleware platform. It combines object-relational SQL storage, RDF graph storage, SPARQL services, web/application server features, and data-integration middleware in one server, with an open-source edition known as OpenLink Virtuoso. ### Historique du projet The Virtuoso project traces back to 1998, when OpenLink's data-access middleware merged with the Kubl DBMS. Kubl itself came from Finnish database work led by Orri Erling in the mid-1990s, and a free trial was publicly available by November 1996 before the technology became the database core of Virtuoso. OpenLink made an open-source edition available under GPLv2 in April 2006 while continuing to offer commercial Virtuoso editions. The public GitHub repository for virtuoso-opensource dates from 2012, and GitHub releases list the open-source 7.2 series as actively maintained into the 2020s. Virtuoso's history is closely tied to Semantic Web and Linked Data adoption. Its SPARQL endpoint support implemented the emerging W3C SPARQL Protocol work during the mid-2000s, and the server became a familiar backend for large RDF datasets and public SPARQL endpoints. ### Historique d'adoption Virtuoso's most visible cultural footprint is in Linked Data infrastructure. DBpedia, one of the canonical Semantic Web datasets, made structured Wikipedia-derived data queryable using OpenLink Virtuoso, and the public DBpedia SPARQL endpoint exposed the familiar Virtuoso query editor to generations of RDF users. W3C's Semantic Web wiki describes OpenLink Virtuoso as a SQL-ORDBMS and web application server hybrid that provides SQL, XML, and RDF data management in a single multithreaded process. That hybrid identity helped it appeal both to database administrators and to RDF practitioners who needed SPARQL, ODBC/JDBC, and web protocols in the same deployment. ### Modes d'utilisation In package-manager contexts, Virtuoso is usually installed for local RDF stores, SPARQL endpoints, DBpedia mirrors, or multi-model database experiments. Users configure a `virtuoso.ini`, run the `virtuoso-t` server, and interact through command-line tools such as `isql`/`isqlw`, HTTP endpoints, SPARQL, ODBC, or JDBC clients. The package matters to developers who need a serious local triplestore rather than an embedded library. A typical package-nerd workflow is to load RDF dumps, expose `/sparql`, tune memory and checkpoint settings in the INI file, and then query large graph datasets with SPARQL clients or browser-based query forms. ### Pourquoi les passionnés de paquets s'y intéressent Virtuoso is one of the few database packages that appears simultaneously in SQL, RDF, Linked Data, and web-middleware histories. For package people, it is the old-school heavyweight triplestore you install when toy RDF stores are not enough and when compatibility with DBpedia-style workflows matters. ### Chronologie - 1996-11-07: A free trial version of Kubl RDBMS was made available. - 1998: Virtuoso began from the merger of OpenLink data-access middleware and Kubl DBMS. - 2006-04: OpenLink made an open-source edition of Virtuoso available under GPLv2. - 2008: SPARQL 1.0 became a W3C Recommendation, strengthening Virtuoso's RDF query role. - 2012: The public virtuoso-opensource GitHub repository was created. - 2015: GitHub releases list Virtuoso Open Source Edition v7.2.0. - 2026: GitHub releases list Virtuoso Open Source Edition v7.2.17. ### Related projects - Kubl DBMS is the direct database predecessor. DBpedia is the most famous public Linked Data deployment associated with Virtuoso. SPARQL, RDF, ODBC, JDBC, and OpenLink Data Spaces are adjacent technologies and products in the same ecosystem. ### Sources - DBpedia article noting Virtuoso-backed data access: https://en.wikipedia.org/wiki/DBpedia - OpenLink Virtuoso SPARQL endpoint documentation: https://docs.openlinksw.com/virtuoso/rdfsparqlprotocolendpoint/ - OpenLink Virtuoso documentation: https://docs.openlinksw.com/virtuoso/ - OpenLink Virtuoso homepage: https://virtuoso.openlinksw.com/ - OpenLink Virtuoso open-source GitHub repository: https://github.com/openlink/virtuoso-opensource - W3C Semantic Web wiki page for OpenLink Virtuoso: https://www.w3.org/2001/sw/wiki/OpenLink_Virtuoso - Wikipedia article on Virtuoso Universal Server: https://en.wikipedia.org/wiki/Virtuoso_Universal_Server ## Notes de sécurité Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour virtuoso. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: virtuoso.ini in the server startup/current directory ## Autres enregistrements de gestionnaires de paquets - MacPorts - virtuoso: normalized package name match | MacPorts ports tree: devel/virtuoso/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 - Debian apt - python3-inifile - 0.4.1-2: installed executable or alias match | Debian stable package indexes: python3-inifile from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Small INI library for Python 3 | https://github.com/mitsuhiko/python-inifile - Ubuntu apt - python3-inifile - 0.4.1-2: installed executable or alias match | Ubuntu 24.04 LTS package indexes: python3-inifile from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Small INI library for Python 3 | https://github.com/mitsuhiko/python-inifile ## Combined YAML source View the package source record on GitHub. [combined/virtuoso.yml](https://github.com/mxcl/pkgdb/blob/main/combined/virtuoso.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph