RFC for PHP Guidelines Update

[Remi Collet]

Please read the draft :
http://fedoraproject.org/wiki/PackagingDrafts/PHP

* Requires and Provides
* Macros and scriptlets

And give feedback before this being proposed to FPC.

Comments on "channels" are also welcome ;)

Remi.

[Joe Orton]

On Tue, Jul 17, 2007 at 07:30:10AM +0200, Remi Collet wrote:
> Please read the draft :
> http://fedoraproject.org/wiki/PackagingDrafts/PHP
> Requires and Provides
> Macros and scriptlets
>
> And give feedback before this being proposed to FPC.

+1, looks good, thanks for writing this up.

joe

[Tim Jackson]

Remi Collet wrote:
> Please read the draft :
> http://fedoraproject.org/wiki/PackagingDrafts/PHP

Thanks Remi!
> Comments on "channels" are also welcome ;)

I've been meaning to say it for a while, but if anyone wants to try the
latest (CVS) version of PEAR_Command_Packaging, I did add support for both:

a) building channel packages, and
b) building packages that require external channels

modelled around Chris S's PHPUnit3 package and associated channel.

Not heavily tested but any feedback would be welcome.

Tim

[Remi Collet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Jackson a écrit :
> I've been meaning to say it for a while, but if anyone wants to try the
> latest (CVS) version of PEAR_Command_Packaging, I did add support for both:

Well, I'm working on this.

Make first SRPM available :

http://rpms.famillecollet.com/SRPMS/php-pear-PEAR-Command-Packaging-0.1.3-0....

What I've done :
- - update the fedora specific patch (don't know if all is needed)
- - update the fedora template.spec
- - add the fedora template-channel.spec

In both, I change the name of the .xml to %{name} (we could encounter
conflict if we only use %{pear_name}). %{name} seems a robust solution.

I cannot change the default for doc_files_relocation_script and
doc_files_statement...

Channel generated spec seems ok.

There is an issue in the generated extension spec in the uninstall command.

In template : @possible_channel@%{pear_name}
Generated :   components.ez.no%{pear_name}

We need a / between channel and extension name.

All seems ok with the PHP Guideline draft Update
https://fedoraproject.org/wiki/PackagingDrafts/PHP

Remi,
Regards.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkl/PjAACgkQYUppBSnxahijIQCg09DGHFdF5DCYsnxzRt5yjV5w
> 2O4AoL6uN+Kh22Leh1tvZKNf1kU+V2XO
> =S781
> -----END PGP SIGNATURE-----

[Remi Collet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Remi Collet a écrit :
> There is an issue in the generated extension spec in the uninstall command.
>
> In template : @possible_channel@%{pear_name}
> Generated :   components.ez.no%{pear_name}
>
> We need a / between channel and extension name.

Same issue with the virtual Provides:
Provides: php-pear(@possible_channel@%{pear_name}) = %{version}

I can't add the / in the template because we don't want it for standard
channel.

Remi
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkl/P7QACgkQYUppBSnxahg/1gCfW68wZen79QVZ19c55/bTaNII
> 3SwAn2e7JLY1jsVM7Ay9fb+fcY71l4TG
> =WU5s
> -----END PGP SIGNATURE-----