On 7 July 2016 at 19:53, Aaron M. Ucko wrote: | Dirk Eddelbuettel <e...@debian.org> writes: | | > What we have works. Making a change risks having to pick up pieces of | > shrapnel. I don't really have time for that --- I cannot test for every | > random piece of software being present. | | I see your point, but am simply asking for more robust handling of one | specific corner case that turned out to be broken. Adding that one | check would have no effect in any other cases. Would you rather require | that every single r-* package either build-depend on xauth or | build-conflict on xvfb?
Think this through: at the extreme you are asking me to reimplement the package management system by avoiding one of over 20k packages. That makes no sense. Most r-cran-* package do not use either: edd@max:~/src/debian/CRAN$ ls -l */debian/control | wc -l 134 edd@max:~/src/debian/CRAN$ grep xauth */debian/control | wc -l 21 edd@max:~/src/debian/CRAN$ (Counts approximate as I may have two versions of a package, but I recently trimmed the directory so that may be a handful at most and can be ignored here.) This could have happened to any one of these 134 - 21 = 113. But generally it doesn't. I really think we should close this, and I plan to. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
