Re[2]: [PEAR-DEV] Re: Version naming

From: Date: Thu, 16 Dec 2004 16:35:13 +0000
Subject: Re[2]: [PEAR-DEV] Re: Version naming
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-35109@lists.php.net to get a copy of this message
Hello Greg, >>> LS> currently the state is not part of the .tgz name. >>> LS> Adding the state was one of the intentions of the original RFC, but >>> LS> people didnt like having it in the version name and some people dont >>> LS> like it being in the .tgz name. >>> >>> Why not to have status information in .tgz? >>> Do tell me it is inconvenient to know what status has downloaded >>> package? Esp. if there are two or more different versions downloaded >>> into one directory. >> >> I dont know honestly .. there were some comments in that direction a >> month or so ago on this list. Try searching for that in the archive. GB> $ pear info Package-1.3.5.tgz GB> putting it in the name is unnecessary, and complicates things. I've GB> written 448 unit tests so far for the installer, and am only about 75% GB> of the way through. Adding this would cause a serious amount of extra GB> validation. I would have to allow GB> Package-version-state GB> Package-state-version GB> Package-version GB> Package-state Only Package-version-state.tgz and Package-version.tgz If you want I can write these tests for you. Just tell where from to start. GB> and would have to not allow GB> Package-version-version GB> Package-state-state GB> The server side would also become much more complicated, and since the GB> question of "how stable is this package" can be answered by the use of GB> pear info and pear remote-info, I see no benefit in adding this extra work. But what about hostings with PEAR installed? I doubt they will allow executing "pear info" script. My shell session to upgrade scripts on such server will be something like uploading package, then tar -xzvf package.tgz So if I want to upload only stable version - I will have to choose packages without any prefixes. It is much better than checking all available files from machine, which have PHP+PEAR installed. GB> I haven't even started to tackle the web frontend - considering how long GB> this will take, any features that are even slightly complicated will GB> have to wait. t --

« previous php.pear.dev (#35109) next »