Re: solution for BC breakage
| From: | Stefan Neufeind | Date: | Tue, 16 Sep 2003 14:31:12 +0000 |
| Subject: | Re: solution for BC breakage | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21573@lists.php.net to get a copy of this message | ||
On 16 Sep 2003 at 16:16, Tomas V.V.Cox wrote:
> On Tuesday, September 16, 2003 15:05, Greg Beaver wrote:
>
> > Hi,
>
> > The answer to the problem of BC is to create a new dependency
> > relation called majorversion
>
> > <dep type="pkg" rel="majorversion"
> > version="1">MDB</dep>
>
> > This can be coupled with another dependency if a particular minor
> > version is needed
>
> > <dep type="pkg" rel="majorversion"
> > version="1">MDB</dep>
> > <dep type="pkg" rel="ge" version="1.5">MDB</dep>
>
> > Comments?
>
> <dep type="pkg" rel="ge" version="1">MDB</dep>
> <dep type="pkg" rel="lt" version="2">MDB</dep>
Hmm, while we're at this: Does it work for larger numbers? Don't know
if we already have that problem but what if a package "9.0" later
becomes "10.0", which propably will one day. Does this already work?
Or would 10 be recognized as being between 1 and 2? Or that 1.0.30 is
larger than 1.0.4.
And if those things are parsed correctly, aren't things like 1.5.0RC2
a problem since they don't follow this numberin-scheme?
Stefan