Bug#2807: X <-> cpp dependency?

[david@elo.ods.com (David Engel)]

> > A better arrangement might be to make the gcc package a superset of
> > the cpp package and have it provide and conflict with the cpp package.
>
> That's exactly what I want.  It's a pretty simple arrangement to
> achieve:
>
> 1. Add a virtual package cppv (it can't be cpp as cpp has to conflict with
>    it).

I don't see any need for a virtual package.

> 2. Have gcc and cpp both provide and conflict with cpp.
> 3. Have gcc and cpp both provide a symbolic link /lib/cpp pointing into
>    the appropriate place.
> 4. Both the cpp and gcc package should contain the info and man pages for cpp.
>
> I see you're the maintainer of cpp.  Could you get together with the
> gcc maintainer to make this happen?  Actually, why are they not
> maintained by the same fellow?  Obviously they're derived from the same
> source.  Perhaps you could just get together with Siggy Brentrup and
> add cpp rules to his debian.rules?  Simplicity is good.

Siggy was the maintainer for binutils, gcc/cpp and several other
packages but he disappeared weeks ago and hasn't been heard from
since.  As I did with libc, I stepped in and took them over on an
interim basis until soneone else can be found.  Would you like to take
them over?

David
--
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081