Howdy X Force! After recursively purging all *-dev packages, I'm always left with the following 5 X11 packages:
libx11-dev libxext-dev libxi-dev libxkbfile-dev x-dev
Looking closer, it appears caused by remaining dependency recursions. My
analysis of the dependency tree showed the following findings:
libx11-dev
* libxi-dev (recursive)
* libxext-dev (dep for libxi-dev or libx11-dev, not both)
* libxkbfile-dev
* x-dev (remove: already dep for libxext-dev and libxkbfile-dev)
libxi-dev
* libx11-dev (recursive)
* libxext-dev
* x-dev (remove: already dep for libxext-dev)
libxext-dev
* x-dev
libxkbfile-dev
* x-dev
x-dev
* (no dep)
As the above shows, a good share of remaining recursion could be
eliminated by removing those redundant dependencies on x-dev.
Then, deciding which of libx11-dev or libxi-dev should depend upon
libxext-dev would eliminate another level of recursion.
Remains one last recursion between libx11-dev and libxi-dev. However,
given how I don't know anything about X11 internals, I'm at loss as to
which one would best depend on the other, on top of the dependency tree.
Hopefully, the above dependency analysis was usefull and could be used
to tune debian/control for the next Unstable upload.
Best Regards,
--
Martin-Éric Racine
http://q-funk.iki.fi
signature.asc
Description: This is a digitally signed message part
