Re: Re: Conditional package dependencies?
| From: | Helgi Þormar Þorbjörnsson | Date: | Mon, 11 Jun 2007 19:10:00 +0000 |
| Subject: | Re: Re: Conditional package dependencies? | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47015@lists.php.net to get a copy of this message | ||
On 6/11/07, Gregory Beaver <greg@chiaraquartet.net> wrote:
Helgi Þormar Þorbjörnsson wrote: On 6/11/07, *Olivier Guilyardi* <ojaiml@nerim.net <mailto:ojaiml@nerim.net>> wrote:Gregory Beaver wrote:Olivier Guilyardi wrote:If I understand correctly you mean that: - SDG_DS_SQLQuery 1.0.x wouldn't provide any file by its ownbut depend on:- SDG_DS_SQLQuery 1.1.x would provide the new driver's files- PHP4 - SDG_DS_DBQuery (the old DB-based driver) - SDG_DS_MDB2 (the old MDB2-based driver)
and depend on:- Structures_DataGrid would depend on:- PHP5
- SDG_DS_SQLQuery >= 1.0Then the pear installer would download the 1.0.x version if it
detects PHP4, andthe 1.1.x or later version otherwise. Is this right? This is indeed the solution I'm talking about. Be forewarned
that thiswill result in some really long version numbers like 1.0.48 and
1.1.94if you do a lot of releases :).
Actually, I don't see any reason to release anything else that 1.0
in the 1.0.x
series. Whenever we release a new version of SDG_DS_DBQuery or
SDG_DS_MDB2, the
pear installer should install the latest PHP4-compatible version.
And what's wrong with normal numbering starting from 1.1? We could
release 1.2,
1.3, etc.. as long as 1.0 is the only release that's not
compatible with PHP5.
Am I right?Wrong, you can't break BC after a stable release unless you make a major version. Hi, Helgi, I think you may have misread what Olivier is saying. 1.0.x/1.1.x would be backwards compatible, the question was whether they can't just go to 1.2.x (php5 + new fangled features) from 1.1.x (php5) as long as 1.0.x is always the PHP4 version. The answer is yes :) Ahh I see what you're saying