Re[2]: [PEAR-DEV] Re: Version naming
| From: | anatoly techtonik | Date: | Fri, 10 Dec 2004 14:28:51 +0000 |
| Subject: | Re[2]: [PEAR-DEV] Re: Version naming | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-35001@lists.php.net to get a copy of this message | ||
Hello Greg,
>> To distinguish between production and not-well for production packages
>> version can be built as 1.0.0RC1 or 1.0.0-beta and you can just check
GB> the "-" is reserved for end-user command-line stuff like
GB> $ pear install DB-beta
GB> this will download the latest beta version of DB, as DB-alpha will
GB> download the latest alpha version.
GB> $ pear install DB-1.6.8
GB> will download version 1.6.8
Ok. Clear to me. The status is independent of version. The string
<version>1.2.0dev</version> in package.xml is incorrect and should
not validate. The question was provoked by the last XML-RPC commits.
If we touched this issue anyway, why not to have a space to delimiter
parameters? Ok, to be able to install several packages at once. Got
this. But this isn't yet reflected in command line help for "install"
command. PEAR 1.3.3.1 I think.
Also will PEAR redistribute alpha and beta packages in .tgz format?
What is file naming convention in this case?
BTW, how to get PEAR version from command line if "pear list" yells
(no packages installed)?
t
--