php5universe

Differences between revisions 2 and 3
Revision 2 as of 2007-06-10 15:26:37
Size: 2404
Editor: host10-47-dynamic
Comment: First definition
Revision 3 as of 2007-06-20 13:19:09
Size: 2536
Editor: ns1
Comment:
Deletions are marked like this. Additions are marked like this.
Line 56: Line 56:
We have ready for test and revision, the first version of '''php5-universe sources''': http://revu.tauware.de/details.py?upid=5637

Summary

Debian provides a source package called php5 which includes, among others, three binary packages: php5-imap, php5-interbase and php5-mcrypt. They are non provided in Ubuntu's php5 since they build-depend on packages which lie in Universe component (libc-client-dev, firebird2-dev and libmcrypt-dev respectively), while php5 lies in Main component.

Rationale

There are several packages which depend on those packages and can not be installed. Here they are:

  • Unmetdeps for php5-imap
    • phpgroupware
    • egroupware-felamimail
    • twig
    • gosa
    • imp4
  • Unmetdeps for php5-interbase
    • ibwebadmin
  • Unmetdeps for php5-mcrypt
    • phpmyadmin

See also part of Ubuntu changelog:

   - debian/control, debian/rules: Disable a few build dependencies and
     accompanying binary packages which we do not want to support in main:
     + firebird2-dev/php5-interbase (we have a separate php-interbase source)
     + libc-client-dev/php5-imap (we have a separate php-imap source)
     + libmcrypt-dev/php5-mcrypt (separate php-mcrypt source)

Use cases

  • Martin is an Ubuntu user which does use phpmyadmin to manage his databases on an AMD64 platform. He is unable to use it without php5-mcrypt due to [https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/114044 bug #114044].

  • Andrew is an Ubuntu user. He uses phpgroupware to manage his activities and he is unable to run it anymore.

Scope

This specification is meant to provide php5-imap, php5-interbase and php5-mcrypt in Gutsy.

Design

We should provide those packages using a single source package (named php5-universe, for instance) which groups these three binary packages. This way it is sufficient to upload only a source package when there is need to instead of having multiple uploads.

In order to keep it synced as much as possible with upstream source package, we should define a strategy which can easily merge changes in.

Implementation

We have ready for test and revision, the first version of php5-universe sources: http://revu.tauware.de/details.py?upid=5637

BoF agenda and discussion


CategorySpec

php5universe (last edited 2008-08-06 16:41:19 by localhost)