In the scope of #19:
According to the Debian policy manual, the naming convention for *.deb files is Foo _ ver - rev _ arch.deb (link).
For clarity, I propose the same convention for raw archives (*.tar and *.zip) so that file names of package archives in different formats differed only in extension.
While the distinction between upstream version and distro revision is something we are just beginning to track (and can be dealt with in a forward-compatible way), the use of correct separators is essential for deployment tools to work.
We currently have the following offenders (ls is used due to its concise output — find produces an exactly similar list):
lxe@WALNUC:~/Code/mxe-shared$ ls src/*_*.mk
src/json_spirit.mk src/sdl2_gfx.mk src/sdl_mixer.mk
src/libatomic_ops.mk src/sdl2_image.mk src/sdl_net.mk
src/libgpg_error.mk src/sdl2_mixer.mk src/sdl_pango.mk
src/liblastfm_qt4.mk src/sdl2_net.mk src/sdl_rwhttp.mk
src/pdflib_lite.mk src/sdl2_ttf.mk src/sdl_sound.mk
src/qtserialport_qt4.mk src/sdl_gfx.mk src/sdl_ttf.mk
src/qtsparkle_qt4.mk src/sdl_image.mk src/t4k_common.mk
IOW, it's exclusively SDL, qt4 and four solitary exceptions.
The packaging update to mxe.postbuild.sh I am currently working on introduces the following policy: all _ (undescore) signs in package names will be substituted with - (minus) in package archive names (i.e. in the "Foo" term of the equation above).
All other printable non-whitespace characters in the package names look good and will stay intact. (Debian also has a lowercase file name policy, but neither FAT nor NTFS are case-sensitive anyway, at least in their default setups.)
No build or pre-build step will be affected, only post-build. No action is currently required or requested. I am posting this issue as a heads up and a suggestion that, going forward, underscores were not used in package names.
In the scope of #19:
According to the Debian policy manual, the naming convention for
*.debfiles isFoo _ ver - rev _ arch.deb(link).For clarity, I propose the same convention for raw archives (
*.tarand*.zip) so that file names of package archives in different formats differed only in extension.While the distinction between upstream version and distro revision is something we are just beginning to track (and can be dealt with in a forward-compatible way), the use of correct separators is essential for deployment tools to work.
We currently have the following offenders (
lsis used due to its concise output —findproduces an exactly similar list):IOW, it's exclusively SDL, qt4 and four solitary exceptions.
The packaging update to
mxe.postbuild.shI am currently working on introduces the following policy: all_(undescore) signs in package names will be substituted with-(minus) in package archive names (i.e. in the "Foo" term of the equation above).All other printable non-whitespace characters in the package names look good and will stay intact. (Debian also has a lowercase file name policy, but neither FAT nor NTFS are case-sensitive anyway, at least in their default setups.)
No build or pre-build step will be affected, only post-build. No action is currently required or requested. I am posting this issue as a heads up and a suggestion that, going forward, underscores were not used in package names.