You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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.
The text was updated successfully, but these errors were encountered:
In the scope of #19:
According to the Debian policy manual, the naming convention for
*.deb
files isFoo _ 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):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.
The text was updated successfully, but these errors were encountered: