| commit | 6bee433ce77c7f26faab709a223d77f7e6d1e40e | |
| author | Thomas Leonard <talex5@gmail.com> | |
| Thu, 17 Jun 2010 20:34:24 +0000 (17 21:34 +0100) | ||
| committer | Thomas Leonard <talex5@gmail.com> | |
| Sun, 20 Jun 2010 19:11:16 +0000 (20 20:11 +0100) | ||
| tree | c7699c653dbefa175c8c27cbb24083eecd4514bb | treesnapshot (tar.gz zip) |
| parent | 459f532d64de1671cc3e13a88687c3c9f1e1cdf3 | commitdiff |
Model information about distribution packages as separate feeds
Before, reading in a feed containing a <package-implementation> element
would expand this to a list of packages provided by the distribution's
package manager (installed or not) and include them in the feeds
'implementations'.
Now, feed with such an element has a corresponding "distribution feed", which
is the feed's URL prefixed with "distribuion:". This feed contains the
distribution packages.
Initially, it contains only installed packages. After updating it, it may
also contain candidate (uninstalled) version.
This has two advantages:
- The loaded representation of feed no longer depends on the host
distribution, which is cleaner.
- Fetching candidates can be done asynchronously.
Before, reading in a feed containing a <package-implementation> element
would expand this to a list of packages provided by the distribution's
package manager (installed or not) and include them in the feeds
'implementations'.
Now, feed with such an element has a corresponding "distribution feed", which
is the feed's URL prefixed with "distribuion:". This feed contains the
distribution packages.
Initially, it contains only installed packages. After updating it, it may
also contain candidate (uninstalled) version.
This has two advantages:
- The loaded representation of feed no longer depends on the host
distribution, which is cleaner.
- Fetching candidates can be done asynchronously.