cuetools 1.3-2 source package in Ubuntu

Changelog

cuetools (1.3-2) unstable; urgency=low


  * The "Overfiend" release, including the 'omnibus' 01_cuetools.dpatch by
    Branden Robinson. His changelog follows. closes: #324977

  * Make several fixes and enhancements to the cuebreakpoints, cueconvert, and
    cueprint commands:
    + Fix them to use an int instead of a char to store the return value of
      getopt_long(), so that the value is not truncated. closes: #324461
    + Enhance usage messages:
      - Store the command synopsis in a static buffer.
      - Report the command synopsis in error as well as "--help" conditions.
      - Summarize the purpose of the command in the usage message.
      - Note default behavior where applicable.
      - Cross-reference manual page.
      - Communicate in complete sentences more.
    + Standardize presentation of error messages.  Always report the command
      name and always say "error:" on error conditions.
    + Make some error message indicate what operation failed instead of
      uttering amorphisms like "input file error".
    + Stop throwing away the value of the function that each program's main()
      wraps.  Instead, store it and use it as the command's exit value instead
      of exiting with status zero no matter what went wrong.
    + Use strcasecmp() instead of strcmp() when attempting to parse file
      format extensions, so that people pulling files from uppercase-happy
      operating systems are less likely to be frustrated.
    + Add some braces in some places to prevent usage(1) from being called
      whether or not the arguments have been successfully parsed or not.
      closes: #324462
    + Add lots of comments.
      - Document symbols required from #included system headers.
      - Document the core logic of main().
      - Add some TODO items with ideas that occurred to me.
    + Make style fixes:
      - Kill extraneous whitespace at ends of lines.
      - Wrap lines at 80 columns.
      - Replace ugly multline string literals (with the newline escaped, or
        GCC would have caught this) with a more idiomatic usage.
      - Write function calls consistently.
      - Use idiomatic multi-line comment style.
      - Use complete sentences in non-TODO comments.
      - Refer to argv[0] as argv[0] instead of *argv (idiom again).

  * Make several fixes and enhancements to the cuebreakpoints, cueconvert, and
    cueprint manual pages:
    + Fix .TH directive:
      - Use the command's own name, not "cuetools".
      - Add the date of last modification and the upstream source
        distribution.
    + Fix the NAME section:
      + Move the command's short description here from the DESCRIPTION
        section, so that whatis(1) and apropos(1) have a chance of finding these
        manual pages.
    + Fix the SYNOPSIS section to more usefully synopsize the command's
      usage.  "[ option ... ] [ file ... ]" is only appropriate for very
      complex commands, in my opinion.
    + Move material from non-standard section names into the DESCRIPTION
      section.
    + Move the DESCRIPTION section to precede the OPTIONS section.
    + Fix the items in the OPTIONS section so that they present correctly.
    + Add an EXIT STATUS section.
    + Fix markup of cross-references in SEE ALSO section.
    + Add myself to AUTHORS section, identifying what I did.

  * Make several fixes to debian/rules:
    + Kill off trailing whitespace from lines in debian/rules.
    + Fix phony targets to only depend on stamp targets in debian/rules.
    + Add configure (phony) and configure-stamp targets to run ./configure,
      and make the build target depend on it.

  * Also bump Standards-Version to 3.6.2, no changes required.
  * Add Build-Depends on dpatch for Branden's patch.

 -- Joshua Kwan <email address hidden>  Sat, 27 Aug 2005 22:09:18 -0700