# eiffelstudio を Homebrew, MacPorts, Nix, pacman, zypper でインストール

eiffelstudio のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:eiffelstudio
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install eiffelstudio
```

  証拠: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install eiffelstudio
```

  証拠: MacPorts ports tree: lang/eiffelstudio/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#ec
```

  証拠: nixpkgs package indexes: pkgs/by-name/ec/ec/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S editorconfig-checker
```

  証拠: Arch Linux sync databases: editorconfig-checker from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install editorconfig-checker
```

  証拠: openSUSE Tumbleweed package metadata: editorconfig-checker from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

## パッケージ情報

- **パッケージキー:** brew:eiffelstudio
- **パッケージマネージャ:** Homebrew
- **バージョン:** 25.02.98732
- **ソース概要:** Development environment for the Eiffel language
- **ホームページ:** <https://www.eiffel.com>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- compile_all (エイリアス)
- ec (エイリアス)
- ecb (エイリアス)
- estudio (エイリアス)
- finish_freezing (エイリアス)
- iron (エイリアス)
- syntax_updater (エイリアス)
- vision2_demo (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 25.02.98732
## プロジェクトの歴史と使われ方

EiffelStudio is the IDE, compiler, debugger, and command-line toolchain for the Eiffel programming language. It is historically important because it carries Eiffel's Design by Contract culture from the commercial ISE Eiffel era into a still-packaged open source development environment.

### プロジェクトの歴史

Eiffel Software describes itself as recognized since 1985 for making software projects predictable and controllable, with EiffelStudio as its flagship IDE. The EiffelStudio documentation presents the tool as the interactive development environment for Eiffel, including an IDE, compiler, debugger, project settings, command-line compiler, and release notes.

The public source history is unusual by modern GitHub standards. The EiffelStudio README states that the main public source repository is an official Subversion repository at svn.eiffel.com, while the GitHub repository is a mirror of trunk. That makes EiffelStudio a packaged survivor of an older vendor-hosted source-control era rather than a GitHub-native project.

The documentation tree preserves long release-note and compiler-history chains, including EiffelStudio 5.x, 6.x, 7.x, and year-based releases through the 2010s and 2020s. This gives packagers a rare long-lived IDE/compiler stack with decades of compatibility decisions embedded in its release history.

### 採用の歴史

EiffelStudio adoption is tied to Eiffel's niche but durable community: universities, long-lived industrial systems, and developers interested in Design by Contract, void-safety, and strongly specified object-oriented programming. It is not a mass-market compiler package, but it matters to users who need the canonical Eiffel implementation.

The input package metadata lists Homebrew, MacPorts, and Nix coverage, which reflects the practical need to keep the toolchain available on developer machines even as the wider programming-language ecosystem moved toward package managers and language servers.

### 使われ方

Users create or open Eiffel projects, edit classes, compile through the graphical IDE or command-line compiler, debug applications, inspect metrics, and manage project settings stored in Eiffel configuration files. Homebrew exposes both GUI and CLI-oriented executables such as estudio, ec, ecb, iron, compile_all, and finish_freezing.

EiffelStudio also anchors Eiffel's project format. The `*.ecf` Eiffel Configuration File is package-relevant because it is the metadata file that tells the compiler how to build a system, much like a project file in other compiled-language toolchains.

### パッケージ好きにとっての重要性

EiffelStudio is package-nerd significant because it is a full language distribution rather than a single CLI: compiler, IDE, libraries, project metadata, code generation, and platform-specific integration all move together. That makes it a heavier formula than most modern Go or Rust binaries.

It also illustrates how package managers preserve minority programming-language ecosystems. Even if Eiffel is niche, Homebrew and peers keep a reproducible path to the canonical toolchain, and that is exactly the sort of long-tail utility package indexes are good at.

### タイムライン

- 1985: Eiffel Software traces its recognition in Eiffel tooling and methods to this period.
- 2000s: EiffelStudio 5.x and 6.x release-note histories appear in the official documentation tree.
- 2010s: The documentation records EiffelStudio 7.x and year-based releases such as 13.11, 14.05, 15.x, and later.
- 2016-06-12: The official GitHub mirror is created.
- 2026-01-20: Eiffel.org documentation metadata shows the EiffelStudio documentation page updated.

### Related projects

- The Eiffel programming language and Design by Contract method are the central context for EiffelStudio.
- ISE Eiffel is the historical naming lineage visible in compiler-history pages.
- The Eiffel libraries and Iron package tooling are related parts of the broader Eiffel ecosystem.

### ソース

- <https://www.eiffel.com/company/about-us/>
- <https://www.eiffel.org/doc/eiffelstudio>
- <https://github.com/EiffelSoftware/EiffelStudio#readme>
- <https://github.com/EiffelSoftware/EiffelStudio>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals


## 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: *.ecf
## 他のパッケージマネージャ記録

- MacPorts - eiffelstudio: normalized package name match | MacPorts ports tree: lang/eiffelstudio/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- MacPorts - ecb: installed executable or alias match | MacPorts ports tree: editors/ecb/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Nix - ec: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/ec/ec/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - ecb - 2.52-1: installed executable or alias match | Arch Linux sync databases: ecb from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Emacs Code Browser | https://github.com/ecb-home/ecb
- pacman - editorconfig-checker - 3.9.0-1: installed executable or alias match | Arch Linux sync databases: editorconfig-checker from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A tool to verify that your files are in harmony with your .editorconfig | https://github.com/editorconfig-checker/editorconfig-checker
- zypper - editorconfig-checker - 3.8.0-1.3: installed executable or alias match | openSUSE Tumbleweed package metadata: editorconfig-checker from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Tool to verify that your files are in harmony with your .editorconfig | https://github.com/editorconfig-checker/editorconfig-checker


## Combined YAML source

View the package source record on GitHub. [combined/eiffelstudio.yml](https://github.com/mxcl/pkgdb/blob/main/combined/eiffelstudio.yml)


## ソース

- 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
