Greetings,
As of changeset 2352 in the pkg(5) gate, the client now allows
publishers to be configured for use with repositories that contain
different sets of package data.
======================================================================
What changed?
======================================================================
Previously, the pkg(5) API assumed that all of the repositories
configured for a single publisher contained the same set of package
data. It would assume it could retrieve the same packages from all
sources, and pick the "best" one to retrieve those packages.
This prevented users from configuring multiple repositories at the same
time for a single publisher such as http://pkg.opensolaris.org/dev and
http://pkg.opensolaris.org/release. If a user attempted to do that, it
would fail. This was the previously intended behaviour as it was
believed that all repositories for a single publisher should have the
same package data.
However, the pkg(5) API has been changed now such that each source
configured for a publisher is checked to determine which packages it
provides, and then the list of packages from all sources is combined
into a single list for presentation by clients.
This will permit users (if package constraints allow it) to mix and
match packages from different repositories for the same publisher.
======================================================================
How can this new functionality be used?
======================================================================
As an example, a user might have http://example.net/repo configured for
the 'mysoftware' publisher:
pkg set-publisher -g http://example.net/repo mysoftware
However, they may have an additional private workspace where they have
development or experimental versions of specific packages for that same
publisher that they want to be install or use for update:
pkg set-publisher -g /path/to/devrepo mysoftware
After performing the above steps, they are free to perform any packaging
operations they would normally, and clients such as pkg(1) will
automatically retrieve package data from the correct source(s).
'install', 'update', 'search', and all other operations will work as
expected.
======================================================================
How could this change impact me?
======================================================================
If you currently rely on the historical behaviour of multiple origins
being treated as all providing the same set of package data, package
clients may currently fail if one of those sources is unreachable when
attempting to refresh package data. This is a known limitation that
will be resolved at a future date.
No other impact is expected from these changes.
======================================================================
What are the related bug entries?
======================================================================
18105 api should support multiple repositories (origins) with different
package data
https://defect.opensolaris.org/bz/show_bug.cgi?id=18105
18107 pkg search returns no results and fails if a publisher with no
origins is present
https://defect.opensolaris.org/bz/show_bug.cgi?id=18107
-Shawn
_______________________________________________
install-discuss mailing list
install-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/install-discuss
