Re: Re: [ANNOUNCEMENT] HTML_Common-1.2.2 (stable) Released.
| From: | Greg Beaver | Date: | Thu, 01 Sep 2005 21:52:17 +0000 |
| Subject: | Re: Re: [ANNOUNCEMENT] HTML_Common-1.2.2 (stable) Released. | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39685@lists.php.net to get a copy of this message | ||
andrew morton wrote:
> On 9/1/05, Klaus Guenther <klaus@capitalfocus.org> wrote:
>
>>There were issues with this release, due to being packed with pear 1.4.0
>>that prevented it from being installable with pear 1.3.x. The release
>>has been pulled and a new release will be rolled shortly.
>
>
> Is there a to build a package that includes the 1.0 and 2.0
> package.xml files? This may be a dumb question but neither the
> pear-dev archives or the package definition entry in the manual
> provided a clear answer. Based on the email I'm replying to I'm not
> the only one who's wondering.
have you tried:
$ pear help package
?
>
> Back in an old thread Greg said: "We've had the support of both a
> package.xml and package.xml 2.0 for *months* - as in PEAR 1.4.0a1 -
> hence package-PEAR.xml and package2.xml in every single commit for the
> PEAR package."
I'll cut and paste for the benefit of future generations from pear help
package:
pear package [options] [descfile] [descfile2]
Creates a PEAR package from its description file (usually called
package.xml). If a second packagefile is passed in, then
the packager will check to make sure that one is a package.xml
version 1.0, and the other is a package.xml version 2.0. The
package.xml version 1.0 will be saved as "package.xml" in the archive,
and the other as "package2.xml" in the archive"
Options:
-Z, --nocompress
Do not gzip the package file
-n, --showname
Print the name of the packaged file.
Regards,
Greg