Re: Re: Version naming

From: Date: Thu, 16 Dec 2004 22:35:13 +0000
Subject: Re: Re: Version naming
References: 1 2 3 4 5 6 7 8 9 10 11  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-35121@lists.php.net to get a copy of this message
anatoly techtonik wrote:
Only Package-version-state.tgz and Package-version.tgz Still not going to do this. Package-state is allowed. You can't just make suggestions without taking a *complete* look at the way things work now. Anything else is a waste of both of our time.
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. PEAR 1.4.0 allows easy synchronization of a remote host with a local copy. No shell scripts needed.
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. I reiterate my first point - please do not make suggestions that clearly show you haven't done more than 10% of the research that needs to be done to understand how things work.
Greg

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