[pkg-horde] sed substitutions in debian/rules for Horde module packages

[Gregory Colpart]

On Thu, Dec 15, 2005 at 02:45:51PM +0100, Lionel Elie Mamane wrote:
> So, would you consider joining the team and having horde-sam be a
> package handled by the team? That last sentence is a bit confusingly
> written, so let me explain how we intend to work: We really, really
> want to avoid the situation where packages are maintained by an
> egalitarian team where everybody is responsible of everything and thus
> everybody relies on the others to do the job and thus nothing
> happens. So we want every package to have one "real" maintainer who
> feels responsible for it; the others in the team *can* help out and do
> uploads. The team is (in my mind) mostly a safety net for when the
> main maintainer is in VAC, over-busy or otherwise unavailable. In the
> case of horde-sam, that one maintainer would naturally be you.

> Technically, we intend to put this mailing list in the "Maintainer:"
> field and people in "Uploaders:"; this is the easiest way to guarantee
> that everyone stays up to date on what happens with the packages (bug
> reports, ...).

OK, it seems good.

$ grep -E ers?: debian/control 
Maintainer: Debian Horde Maintainers <pkg-horde-hackers at lists.alioth.debian.org>
Uploaders: Gregory Colpart (evolix) <reg at evolix.fr>

> Last, but not least: I can't find you on https://db.debian.org/ , are
> you a Debian Developer? If not, do you already have a sponsor for
> horde-sam?

I need a sponsor for my horde-sam packages.
Non-final version (I prepare some patches) can be download here :

http://gcolpart.evolix.net/debian/horde-sam/


> > I'm curious, what is the reason to do that ?
> 
> Horde is meant to be installed all in one directory (tree), but this
> conflicts with the FHS, and thus the Debian policy. So the Debian
> packages put things where the FHS mandates and put up compatibility
> symlinks. The horde code, however, assumes that it can take the name
> of the current file, go up a few levels (two in the case you cite) and
> it will find the horde installation directory (root of the tree). This
> assumption is broken by debian (e.g. a file in /etc/horde/horde3 will
> think the horde root it /etc/ in this fashion, while it is
> /usr/share/horde3). So we hard-code the right root so that everything
> still works.

OK, thanks. Have you an example of file that could think horde root is
"/etc/" ? Because I don't see any *_BASE in config files.


Regards,
-- 
Gregory Colpart <reg at evolix.fr>  GnuPG:1024D/C1027A0E
Evolix - Informatique et Logiciels Libres http://www.evolix.fr/