# Adding the repository to an N900

Two ways. The first is one tap, the second is for when you want to see exactly
what is being written.

---

## Option 1: Application Manager (recommended)

On the phone: **Application Manager**, then the menu, then **Application
catalogues**, then **New**. Four fields.

| Field | Value |
|---|---|
| Catalogue name | `Atrium City extras` |
| Web address | `http://n900.atrium.city/extras/` |
| Distribution | `fremantle` |
| Components | `free non-free` |

| Field | Value |
|---|---|
| Catalogue name | `Atrium City Nokia` |
| Web address | `http://n900.atrium.city/nokia/` |
| Distribution | `fremantle` |
| Components | `nokia` |

Those two are all most people need. The Nokia catalogue adds no applications of
its own; it supplies the platform libraries that make the others installable.

Details that will bite if missed:

- **Keep the trailing slash** on the web address.
- **Components go in one field, separated by a space**, not one per line.
- Leave **Disabled unchecked**.

Optional, if you know why you want them:

| Name | Web address | Distribution | Components |
|---|---|---|---|
| Atrium City testing | `http://n900.atrium.city/extras-testing/` | `fremantle` | `free non-free` |
| Atrium City devel | `http://n900.atrium.city/extras-devel/` | `fremantle` | `free non-free` |

**`extras-devel` is unstable by design.** It is an unfiltered development
repository, and installing from it is the classic way to break a working Maemo
install. Do not enable it on a phone you depend on.

No one-tap install file is offered on purpose. Those add repositories to a
phone without the owner seeing what they are agreeing to.

---

## Option 2: by hand

Create `/etc/apt/sources.list.d/atrium.list` as root:

```sh
deb http://n900.atrium.city/extras/  fremantle free non-free
deb http://n900.atrium.city/nokia/   fremantle nokia
```

and for the full set, additionally:

```sh
deb http://n900.atrium.city/extras-testing/    fremantle free non-free
deb http://n900.atrium.city/extras-devel/      fremantle free non-free
```

Then:

```sh
sudo gainroot
apt-get update
```

### Reading those lines

`fremantle` is the **distribution**, which is the codename for Maemo 5, and it
is what the repository is organised under on disk. `free`, `non-free`, `main`
and `nokia` are **components** within it. The two are independent of the pool
directory layout, so they are the only parts that have to match.

---

## It must be plain HTTP

Not a preference. Maemo 5 ships OpenSSL 0.9.8, which predates TLS 1.2, and its
certificate bundle is from 2009 and predates Let's Encrypt. The device
physically cannot fetch from an HTTPS repository, and no package in any Maemo
repository fixes that. **Use `http://`, never `https://`.**

## The repository is unsigned

There is no `Release.gpg`, which is normal for Maemo and matches how every
Fremantle repository has always worked. apt may warn about unauthenticated
packages. Integrity is covered a different way: every file was verified against
its MD5 from the index at mirror time, and roughly 4% of the upstream source
turned out to be zero-byte files that were caught and repaired rather than
copied.

---

## What you should see

After `apt-get update`, Application Manager lists applications whose section
begins with `user/`. Currently available:

| Repository | Apps visible in HAM |
|---|---|
| extras | 885 |
| extras-testing | 1,365 |
| extras-devel | 3,956 |

The `nokia` component holds the platform libraries rather than applications, so
it will not add entries to the list. It is what makes the applications
installable: without it a large share of them fail with missing dependencies.

## Checking it worked

```sh
apt-cache policy | grep n900.atrium.city
apt-cache show libsdl1.2 | head -5
```

`libsdl1.2` is a good canary. It lives in the Nokia component, nothing in
extras provides it, and roughly 190 applications depend on it. If that returns
a package, the layer that fixes the missing-dependency problem is working.