Source: nasm Version: 2.13.01-2 Severity: wishlist Currently, nasm is involved in a build dependency cycle:
nasm Build-Depends on ghostscript ghostscript Build-Depends on libjpeg-dev libjpeg-turbo Build-Depends on nasm To me, the ideal way to break this cycle would be to split out the documentation into a "nasm-doc" package and then move the associated Build-Depends to Build-Depends-Indep. Otherwise, creating a build profile "stage1" or "nodocs" could also work - though this would be suboptimal, since it would change the package contents, so you would have to rename the resulting package to something like "nasm-stage1" with "Provides: nasm". -- Daniel Schepler
