Do not store full path in GZipped js files. #341
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This cause issues in RPM packaged gems in Fedora, since the files, there appears full path with installation prefix, while in reality, they are later installed on different place. E.g. during package build of Hub [1], the documentation is generated into
/builddir/build/BUILDROOT/hub-1.12.1-3.fc22.noarch/usr/share/doc/hub
directory, while the/builddir/build/BUILDROOT/hub-1.12.1-3.fc22.noarch
prefix is later on stripped when the resulting RPM is generated. This cause issues such as:Aside from this particular issue, I really wonder why generation of the GZipped js files is not just optional. As far as I can say, they are not useful when the documentation is browsed just locally. In this case, it just consume more disk space.
[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=8735163