We can use the output of this to manually create the release if it
fails automatically. We needs the generated paths to provide to the
manual operation in the GitLab GUI.
The ldflags variable is no longer used in the file because it embedded
LDFLAGS from build environment and LibGPhoto2 LDFLAGS, where the former
contains flags from the environment and can cause problems, and the
latter is empty.
With the state above, we can drop ldflags from pkgconfig file
completely.
Currently, there is no way to disable the build of the umax_pp low level
sources because the tool umax_pp is *always* built. Some platforms
cannot build the umax_pp low level code so this causes problems.
This means that commits from the same merge request will always appear
together in the ChangeLog, instead of appearing shuffled together with
other commits that were authored around the same time.
Use 12-digit short hashes (which appear in merge commits). The number
of digits required to unambiguously identify a commit increases as the
Git repository grows. The ChangeLog for the 1.0.27 release has 7-digit
short hashes, which are no longer meaningful: 9 digits are needed now.
Forcing 12 digits to display here is the solution in the Linux kernel.
Do not "decorate" the log with branch or tag names. It is understood
that each file starts at a specific release tag (e.g. 1.0.27) and ends
at the next tag (1.0.28), or at HEAD for development snapshots. Topic
branch names, or the refs "master" and "HEAD", do not need labeling.
The output from the SCSI inquiry command uses fixed-length space-padded
strings, which are copied into null-terminated strings before use.
This is currently done using strncpy(), with the count parameter set to
the string's fixed length. Because a null terminator is not encountered
in the input, strncpy() does not write one in the output, and GCC warns
about potential string truncation. A null terminator is added manually,
but this is error prone (as shown by the fix for the microtek backend).
Use snprintf() instead, which guarantees a null-terminated result and
resolves the warnings from GCC.
With the exception of use in three quotes as well as our inlcuded copy
of the GPL, all use of the Free Software Foundation's postal address
has been removed.
Re #320.
Device nodes are always comprised of alphanumeric characters so
there's no need to quote them. That being said, where appropriate,
use curly braces if the variable doesn't terminate the string -
technically, this isn't necessary as the character which follows
is a dot ('.'), which isn't a legal character in variable names so
there's no ambiguity but it makes the variable "stand out" at the
very least.
The update-upstreams.sh script is kept for the convenience of those who
want or need to use it. It has been slightly modified to provide more
feedback in case of error conditions.
Ralph Little