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
Would it be possible for the github releases to also use a versioned
scheme? The tarball at sourceforge already appears to provide that,
and other github-based projects make this possible too, so it is
a bit odd to see that sourceforge contains more info than github
in this regard. :)
When extracting e. g. the 0.4.0.tar.gz from github, it is expanded
into the longer version, thus the tarball does not match the
name of the archive; the sourceforge release does not have
this problem.
It's not a big issue, I can re-package, but I think it would be
simpler if the versioned name remains the same, the extracted
directory is also the same (such as the sourceforge release)
and the github-releases could also offer these tarballs. Perhaps
there is some simple way in github to do this automatically.
Anyway, thanks for reading, please close this at any moment
in time!
The text was updated successfully, but these errors were encountered:
Hey lx-devs,
On sourceforge I noticed a recent upload:
https://sourceforge.net/projects/lxde/files/LXTerminal%20%28terminal%20emulator%29/LXTerminal%200.4.x/lxterminal-0.4.0.tar.xz
Note how it is versioned.
On github, the URL only offers this:
https://github.com/lxde/lxterminal/archive/0.4.0.tar.gz
Would it be possible for the github releases to also use a versioned
scheme? The tarball at sourceforge already appears to provide that,
and other github-based projects make this possible too, so it is
a bit odd to see that sourceforge contains more info than github
in this regard. :)
When extracting e. g. the 0.4.0.tar.gz from github, it is expanded
into the longer version, thus the tarball does not match the
name of the archive; the sourceforge release does not have
this problem.
It's not a big issue, I can re-package, but I think it would be
simpler if the versioned name remains the same, the extracted
directory is also the same (such as the sourceforge release)
and the github-releases could also offer these tarballs. Perhaps
there is some simple way in github to do this automatically.
Anyway, thanks for reading, please close this at any moment
in time!
The text was updated successfully, but these errors were encountered: