Differences between revisions 1 and 8 (spanning 7 versions)
Revision 1 as of 2014-09-17 08:05:30
Size: 589
Editor: PaulWise
Comment: initial page
Revision 8 as of 2014-09-17 10:28:55
Size: 1809
Editor: PaulWise
Comment: buxy's mail
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Extending the Debian repository format to allow suites enumeration = = Extending Debian repos =

We want to enable:

 * Automatic enumeration of suites for a repository
 * Automatic enumeration of repositories for a distro
Line 17: Line 22:
[https://lists.debian.org/CAKNHny8OUnOveJxOmDNhQHcoFJG4PbKgCh4ZBYwuj5QyvF-eFQ@mail.gmail.com] https://lists.debian.org/CAKNHny8OUnOveJxOmDNhQHcoFJG4PbKgCh4ZBYwuj5QyvF-eFQ@mail.gmail.com

=== reprepro ===

Has a configuration file listing all suites with metadata about all of them.
Line 24: Line 33:

=== piuparts.debian.org ===

Encodes codename combinations like squeeze2bpo2wheezy in a configuration file.

== Requirements ==

=== piuparts.debian.org ===

Want squeeze2bpo2wheezy to not be magically deleted just because jessie became stable. When new stable releases are done, '''new''' piuparts suites (like wheezy2bpo2jessie) should be created, not old ones reused.

=== Single source of data ===

For some purposes it would be interesting to have a single source of all metadata (on a per-repo basis and also on a global distro-wide basis) so that full apt metadata doesn't need to be downloaded if it isn't needed. This could also be easier to parse in some cases.

=== Know which suites are partial ===

Knowing what suites are "partial" (i.e. don't have a full set of packages) and what parent suite they are associated with (to get the remaining packages) is important for example to be able to do proper dependency analysis
on a partial suite by trying to look up missing packages in the parent
suite.

Extending Debian repos

We want to enable:

  • Automatic enumeration of suites for a repository
  • Automatic enumeration of repositories for a distro

This page is for exploring the existing solutions, existing hardcoding and requirements for services.

Existing solutions

distro-info

Has the same problems as hardcoding elsewhere but better than hardcoding in lots of places.

Ubuntu

http://changelogs.ubuntu.com/meta-release

Tanglu

https://lists.debian.org/CAKNHny8OUnOveJxOmDNhQHcoFJG4PbKgCh4ZBYwuj5QyvF-eFQ@mail.gmail.com

reprepro

Has a configuration file listing all suites with metadata about all of them.

Existing hardcoding

sources.debian.net

Please fill me in zack :)

piuparts.debian.org

Encodes codename combinations like squeeze2bpo2wheezy in a configuration file.

Requirements

piuparts.debian.org

Want squeeze2bpo2wheezy to not be magically deleted just because jessie became stable. When new stable releases are done, new piuparts suites (like wheezy2bpo2jessie) should be created, not old ones reused.

Single source of data

For some purposes it would be interesting to have a single source of all metadata (on a per-repo basis and also on a global distro-wide basis) so that full apt metadata doesn't need to be downloaded if it isn't needed. This could also be easier to parse in some cases.

Know which suites are partial

Knowing what suites are "partial" (i.e. don't have a full set of packages) and what parent suite they are associated with (to get the remaining packages) is important for example to be able to do proper dependency analysis on a partial suite by trying to look up missing packages in the parent suite.