Re: Re: Conditional package dependencies?
| From: | Helgi Þormar Þorbjörnsson | Date: | Mon, 11 Jun 2007 18:59:22 +0000 |
| Subject: | Re: Re: Conditional package dependencies? | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47013@lists.php.net to get a copy of this message | ||
On 6/11/07, Olivier Guilyardi <ojaiml@nerim.net> wrote:
Gregory Beaver wrote: Olivier Guilyardi wrote:Wrong, you can't break BC after a stable release unless you make a major version. - Helgion:If I understand correctly you mean that: - SDG_DS_SQLQuery 1.0.x wouldn't provide any file by its own but dependon:- PHP4 - SDG_DS_DBQuery (the old DB-based driver) - SDG_DS_MDB2 (the old MDB2-based driver)- SDG_DS_SQLQuery 1.1.x would provide the new driver's files and dependPHP4, and- PHP5- Structures_DataGrid would depend on:- SDG_DS_SQLQuery >= 1.0Then the pear installer would download the 1.0.x version if it detectsThis is indeed the solution I'm talking about. Be forewarned that this will result in some really long version numbers like 1.0.48 and 1.1.94 if 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?the 1.1.x or later version otherwise. Is this right?