[dev] Introduction

Mathieu Parent math.parent at gmail.com
Sat Jan 12 09:56:52 UTC 2013


2013/1/12 Remi Collet <remi at fedoraproject.org>:
> Hi

Hi Remi,

> I'm new on this list, but, as a common usage, here is a small
> introduction about me.

I'm also new on the list, and have not introduced myself. As I have a
similar background than you, I will do it here ;-)

> Since recently, I start opening bugs[1] about horde components.

Same

> I'm a fedora package maintainer, most in the PHP Stack[2], and also a
> contributor to various OpenSource project.

I'm a Debian Developer (package maintainer), I package Horde, Kolab,
some PHP PEAR packages and ctdb (samba clustering) [0]. I am also a
contributor to some other open source projects (like FreeSWITCH VoIP)

[0]: http://qa.debian.org/developer.php?login=sathieu@debian.org

> We are working on having latest horde applications available in fedora
> repository.
>
> Current horde packages available in Fedora (not an official fedora
> project page, but a quite useful one):
> http://rpms.famillecollet.com/rpmphp/rpm.php?type=pear&what=%23horde

This is almost done on the Debian part:

[1] http://qa.debian.org/developer.php?login=pkg-horde-hackers@lists.alioth.debian.org

We used the "components" application to bootstrap the packages. With
some wrapper around it. Instructions are at:

[2] http://anonscm.debian.org/gitweb/?p=pkg-horde/PEAR/tools.git;a=blob;f=README

Some questions:
- How are your packages bootstraped?
- How do you manage patches?
- How do you manage removed files (non-free files or already compiled ones)
- How do you manage mass-updates?
- Do you run unit tests?

> Current package submission list:
> https://bugzilla.redhat.com/buglist.cgi?list_id=947536&short_desc=horde&classification=Fedora&query_format=advanced&short_desc_type=allwordssubstr&component=Package%20Review&product=Fedora
>
> Yes packaging all the horde components / applications is a huge job ;)

Yes.

> Benefits for the horde project:
>
> - more QA, we always try to, at least, run the test suite during the
> package build and thus, detect any problem / regression ASAP.
>
> - more visibility (even if horde probably don't need this)
>
> - more tests with recent PHP version, as I'm already working on PHP 5.5
> (for Fedora 19)

I will add:
- Better dependency handling and smoother upgrades. As Ralf said: "A
simple pear upgrade -c horde would break your existing installation
because it would upgrade everything to the most recent major version"
[3].

[3]: http://www.ralf-lang.de/2012/12/29/theyre-taking-the-horde-to-debian-to-debian/

> - etc...
>
>
> This ML is probably a better place to "ask" some questions than filling
> bug (such as #11941), and will help me to better understand how the
> project works.
>
>
> Best regards,
> Remi
>
>
> [1] examples:
>     [Tickets #11913] Horde_Mime use preg_replace with eval
>     [Tickets #11894] Horde_Routes: Array to string conversion
>     [Tickets #11943] Horde-Text-Filter  use preg_replace with eval
>     [Tickets #11950] Horde_Editor, move ckeditor to a subdir of js
> [2] https://admin.fedoraproject.org/pkgdb/users/packages/remi


Regards
--
Mathieu Parent


More information about the dev mailing list