Question about maintaining the unofficial/parallel apache-lingerd package.

[Alexis Sukrieh <sukria@sukria.net>]

Hello there.

I'm maintaining an unofficial package, apache-lingerd [1].
It's a new flavour of the official Debian apache source tree.

As it won't be included in Debian, and as some users requested me
to maintain the package against the last sid packages, I'm a little bit
confused :

- If I make a package in my personal repository with a version number
  higher than the official package, users can get confused with apt-get
  upgrade (would upgrade to my apache package even if they don't want my
  lingerd package).

- If I use the same version number, it won't work.
  Indeed, as every flavour, apache-lingerd depends on apache-common
  which provides /usr/sbin/apache-modconf. 
  The official apache-modconf does not support apache-lingerd but 
  my version does.

What would be, to you, the best way of numbering an unofficial package
which is already existing, with the same name in Debian ?

That's a really special case I guess and I haven't found yet a good
solution.

Any help/comment/idea is welcome.

Other advices about maintaining a patched debian package is also
welcome.

Regards,

Alexis.

1 : http://www.sukria.net/packages/apache-lingerd/

-- 
Alexis Sukrieh <sukria@sukria.net>
 
    * Another Linux Debian Geek Enthusiast
    * http://www.sukria.net
    * http://www.debian.org - Just for code.