fedserv/echo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Nest the ircd link under modules/protocol/

Browse source 
The protocol link is a different kind of module from the service
pseudo-clients, so give it its own home: modules/inspircd ->
modules/protocol/inspircd. A future ircd link is a new crate alongside
it. Workspace member, dependency path, the crate's own api path, and the
docs are updated to match. No code change.
This commit is contained in:
Jean Chevronnet 2026-07-14 14:28:18 +00:00
parent ad2a623120
commit a803177f8b
No known key found for this signature in database
5 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -22,9 +22,10 @@ workspace, each depending only on the `fedserv-api` SDK crate.
- **`src/gossip.rs`** node-to-node replication over the logs.
- **`modules/`** the loadable modules, each its own crate depending only on the
`fedserv-api` SDK:
- **`modules/inspircd/`** (`fedserv-inspircd`) the ircd link layer. A `Protocol`
impl maps raw server-to-server lines to and from the normalized model, so the
engine never touches a raw line and a new ircd is one new crate.
- **`modules/protocol/inspircd/`** (`fedserv-inspircd`) the ircd link layer. A
`Protocol` impl maps raw server-to-server lines to and from the normalized
model, so the engine never touches a raw line and a new ircd is one new crate
under `modules/protocol/`.
- **`modules/nickserv/`, `modules/chanserv/`, `modules/botserv/`,
`modules/memoserv/`, `modules/statserv/`, `modules/hostserv/`, `modules/operserv/`**
and diceserv, infoserv, reportserv, groupserv, chanfix, helpserv — the