Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: lilypond - A typesetting system for music notation


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189656


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|163778                      |163779
              nThis|                            |




------- Additional Comments From [EMAIL PROTECTED]  2006-05-19 12:46 EST -------
First off, there are three empty PNG files in the documentation:

E: lilypond-doc zero-length
/usr/share/doc/lilypond-doc-2.8.2/input/mutopia/J.S.Bach/wtk1-fugue2.png
E: lilypond-doc zero-length
/usr/share/doc/lilypond-doc-2.8.2/input/mutopia/W.A.Mozart/mozart-hrn-3.png
E: lilypond-doc zero-length
/usr/share/doc/lilypond-doc-2.8.2/input/mutopia/E.Satie/petite-ouverture-a-danser.png

Any idea about these?  They come that way from upstream.  I guess there's not
much point in including them if they're empty.

Other than that I have no issues.  I do understand your point about the size of
the documentation.  Technically you could build it as a completely separate
package because you're using a different upstream tarball, but once GS 8.50 is
in you'll be able to build it directly and you'd be back to the same problem. 
Or you could just stick with using the upstream tarball.  The packages with
separate -doc packages not built from the main RPM all seem to be shipping
preformatted documentation from upstream.

I'm going to approve this package and leave it to you to fix the three empty
files when you check in.  Or if you like, you can strip the documentation from
the base package and submit a separate package, which I promise to review 
quickly.

APPROVED

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-package-review

Reply via email to