Many other filesystems need it but vfat no longer does. It calls
built-in UTF-8 functions directly, while nominally using nls_ascii
as its I/O charset.
So many module packages depend on core-modules already that almost
every installer image includes it.
The only obvious exceptions are the sh4 installer builds, as there
was no core-modules package on sh4. For consistency, include the
default set of modules in its kernel-image package now.
See commit 0e156c15e3 for the details
about utf8 vs. ascii iocharset for FAT. This fixes a regression with
EFI-related mounts within the Debian Installer.
Signed-off-by: Cyril Brulebois <kibi@debian.org>
By default dpkg-architecture lets the current environment override the
architecture specified by the -a option. We mustn't let that happen
here as we are considering all architectures. Use the -f option to
force use of our specified architecture.
Currently on powerpc, powerpcspe and ppc64 we get an automatic dbgsym
package with symbols for the bootwrapper tools (addnote, hack-coff,
mktree). We should either put them in linux-image-*-dbgsym or
nowhere. For now, opt for nowhere.
Move the dh_strip invocation from the install-base rule to the
install-image_... rule. None of the other packages using install-base
should contain any executables.
I don't know what the suffix is going to be next time we need to add
it, but it will sort lower than the '+deb' suffix added for stable
security updates.
usbip has its own version number which we combine with the source
package version, which is assigned to VERSION for the install-usbip
target (only). We find the version number by processing the config.h
file created by autoconf. The file always exists before the
install-usbip rule is invoked, but the target-specific definition of
VERSION is still evaluated whenever debian/rules.real is used,
resulting in confusing (though harmless) error messages about a
missing file.
We could change VERSION to be a recursively-expanded variable, but
then it would still be evaulated multiple times. Instead, move the
definition of VERSION into the target's commands.
FAT has to convert between Linux filenames ('iocharset' encoding,
should be UTF-8 today) and native filenames (UTF-16 for long names,
'codepage' encoding for short names). And it has to do case
folding in multiple encodings. Unfortunately Linux doesn't
implement case-folding for UTF-8, resulting in inconsistent name
lookup behaviour as shown in bug #833238.
The 'utf8' option makes FAT assume the Linux filename encoding is
UTF-8, regardless of the 'iocharset' encoding. Enabling this and
setting iocharset=ascii mitigates the problems by enabling case-
folding for the ASCII subset.
Make that the default by enabling FAT_DEFAULT_UTF8 and setting
FAT_DEFAULT_IOCHARSET to "ascii".
Ben Hutchings
Cyril Brulebois
Nicolas LE CAM