repository pinning (#575) · Issues · alpine / apk-tools

repository pinning

Apk should be able to load both main and testing repositories, but use packages from testing only if explicitly asked.

Possible syntax: “apk add mypackage@testing” would pin the package to ‘testing’ repository version, including all dependencies. The dependencies should be permanent and stored in world.

(from redmine: issue id 575, created on 2011-04-08, closed on 2011-11-03)

Changesets:
- Revision 500f8d4a by Timo Teräs on 2011-10-29T02:18:21Z:

solver, db: implement repository pinning

Improves /etc/apk/repositories format so you can say:
http://nl.alpinelinux.org/alpine/v2.3/main
@edge http://nl.alpinelinux.org/alpine/edge/main
@testing http://nl.alpinelinux.org/alpine/edge/testing

After which you can pin dependencies to these tags using:
 apk add stableapp newapp@edge bleedingapp@testing

Apk will now by default only use the untagged repositories,
but adding a tag to specific dependency:
 1. will prefer that tag for the name
 2. allowing pulling in dependencies from that tag (though,
    it prefers untagged packages to satisfy deps if possible)

fixes #575

Apk should be able to load both *main* and *testing* repositories, but
use packages from *testing* only if explicitly asked.

Possible syntax: “apk add mypackage@testing” would pin the package to
‘testing’ repository version, including all dependencies. The
dependencies should be permanent and stored in world.

*(from redmine: issue id 575, created on 2011-04-08, closed on 2011-11-03)*

* Changesets:
  * Revision 500f8d4a7d7b17871647392e79e4c7a17c210534 by Timo Teräs on 2011-10-29T02:18:21Z:

```
solver, db: implement repository pinning

Improves /etc/apk/repositories format so you can say:
http://nl.alpinelinux.org/alpine/v2.3/main
@edge http://nl.alpinelinux.org/alpine/edge/main
@testing http://nl.alpinelinux.org/alpine/edge/testing

After which you can pin dependencies to these tags using:
 apk add stableapp newapp@edge bleedingapp@testing

Apk will now by default only use the untagged repositories,
but adding a tag to specific dependency:
 1. will prefer that tag for the name
 2. allowing pulling in dependencies from that tag (though,
    it prefers untagged packages to satisfy deps if possible)

fixes #575
```

Discussion
Designs