Re: Dependencies of metapackages
but if you mean strict "meta" as in it has no files but depends on real specific libraried packages ...
as far as I know strict "meta" are already well versioned and any package, such as perl, acts as a
"meta" in some way by depending on other versions of packages to "fully install" - in the sense of
how you are discussing whether metas can have version - though it has a few initial files installed.
what is important is that metas and virtuals are not mixed together and kept far apart is what I'd say
Vincent Danjean wrote:
On 30/08/2011 16:46, Andreas Tille wrote:
On Tue, Aug 30, 2011 at 11:27:48AM +0100, Wolodja Wentland wrote:
It is my impression that the problems mentioned in my initial mail
solved by changing metapackages (like those mentioned by Cyril in his
reply) to use Recommends instead of Depends.
What happens when a new Recommends is added to a meta-package. Is it
by default by APT ?
Can we add version information (>= X.Y) to Recommends? I'm not sure
useful for the APT point of view.