Re: Re: Allowing one package to virtually "provide" another

bertrand Gugger wrote:

Is there a way of doing this, such that if I split the package in future, a "pear upgrade" will transparently download Foo_Driver_MySQL to maintain the same set of functionality? I can't find anything in the package2.xml spec about this.

What about Foo new version would add a dependency on Foo_Driver_MySQL ? Ah no, name would change.

You could do this, but it would defeat the object of splitting it into a sub-package, because all users would still get BOTH parts. What you want is that after it has been split into a sub package, new users only get the "base" package if they install "Foo".

# First package ... Name: Foo Provides: Foo_MySQL ... # After split, first package: ... Name: Foo ... # After split, second package: ... Name: Foo_MySQL ...

So previously you said yum update Foo getting the whole What you say after the split ? still yum update Foo ? getting the whole ?

Well, just a general "yum update", assuming that the version of "Foo" has been increased. I'm not sure offhand what would happen if you just did a "yum update Foo" - it might work, or might not. Tim