Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

callout gifs copied from docbook #3396

Closed
thkoch2001 opened this issue Mar 9, 2020 · 1 comment
Closed

callout gifs copied from docbook #3396

thkoch2001 opened this issue Mar 9, 2020 · 1 comment

Comments

@thkoch2001
Copy link
Contributor

This issue was part of the rejection reasons in the first review of nix for entrance in the Debian archive, see https://salsa.debian.org/debian/nix/issues/9.

The gif icons in doc/manual/images/callouts/ are copied from docbook: b0a09a6

I can copy the correct copyright for these files from the docbook package:
https://metadata.ftp-master.debian.org/changelogs//main/d/docbook-xsl/docbook-xsl_1.79.1+dfsg-2_copyright

Or I can remove this files from a repackaged source tarball and use the ones from the docbook package.

Or you try how it looks to build the manual without these graphics. If I understand this correct, it is possible to not use graphic files:
http://docbook.sourceforge.net/release/xsl/1.79.1/doc/fo/callout.graphics.html

Related question: Why do you bother to ship a compiled manual.html and manpages in the release tarball at all? It is a source tarball and contains the makefiles to build the docs. For me as a distribution packager it is easier to just build everything from source instead of checking whether I really have the source of everything I distribute.

@edolstra
Copy link
Member

The reason for shipping a compiled manual was to reduce the number of dependencies needed to build Nix (i.e. the same reason for including generated flex/bison output). However, I've been thinking about getting rid of the source tarball entirely, since it doesn't provide a lot of value anymore - people who want to build from source can also just do a Git checkout of the release tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants