On Wed, Oct 15, 2014 at 07:49:08AM -0400, Miles Fidelman wrote: > 1. There is now an essential metapackage called init that depends on > one of systemd-sysv, or sysvinit-core, or upstart. (parenthetical > question: What distinguishes a metapackage from a virtual package? > Or perhaps, more precisely, why is init defined as a metapackage > rather than a virtual package?)
A virtual package doesn't exist, but is listed in Provides: or Requires: fields in other packages. A metapackage does exist, but doesn't contain any files, so only it's metadata is relevant. You may need a metapackage rather than a virtual package for upgrade situations. A metapackage can provide: something else, can Replaces: something else, etc.; whereas a virtual package can't (because it doesn't exist.) > 4. How, in a preseed file, does one identify one's preferred choice > for meeting the dependencies of a virtual package or metapackage (in > this case, specifically installing sysvinit-core to satisfy init's > dependencies) - either by: > a. over-riding package priorities, or, > b. making an explicit selection of the real package to meet a dependency I *think* that if the dependency is already satisfied by another package selection, the resolver won't go out and try to satisfy it with another, as of yet unmarked package. So if you have "d-i pkgsel/include string sysvinit-core systemd-shim" or similar, the resolver shouldn't then select systemd to satisfy the init dependency, as it is already satisfied. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015124455.ga25...@chew.redmars.org
