4 ms·

I saw this before and it always looked like a nice pice of software. The sad part is, it is still at "0 releases". To the developers of this software: please p

by raimue 11y ago

I saw this before and it always looked like a nice pice of software. The sad part is, it is still at "0 releases". To the developers of this software: please provide a stable release that can be packaged for the popular package managers/distributions. That will help to spread the word about your work and make it easily accessible.

snarez 11y ago
OK
- Roritharr 11y ago
  That was quick. https://github.com/snare/voltron/releases/tag/v0.1.1 https://github.com/snare/voltron/releases/tag/v0.1.1
- snarez 11y ago
  There was actually already a v0.1 release on PyPI and had been for some time, it just wasn't tagged on GitHub. The README says to use `pip install voltron`.
boxfire 11y ago
RTFM? Release versions are on pip. Unfortunately most distros think they have the one holy package management solution. pip IS a release and distribution system. With the current popularity of Python, it is only going to be a matter of time before apt / rpm / etc support working through it.
- tomc1985 11y ago
  It is trivial to generate a .deb from nearly any pip module... sudo apt-get install devscripts python-all-dev python-stdeb; cd path~to~pip; python setup.py --command-packages=stdeb.command bdist_deb
  - duaneb 11y ago
    It's trivial to do a lot of niche catering and die by a thousand cuts. It's also trivial to install pip.
    - tomc1985 11y ago
      I'd hardly call debian and its derivatives 'niche', but whatever floats your boat...
      - duaneb 11y ago
        It's not niche in terms of OS deployment, perhaps, but a user's request for a `deb` file over traditional python packaging certainly is.
        tomc1985 11y ago
        Perhaps, but this is to answer the call of 'os-native' packaging. I'd figure between msi+pkg+rpm+deb you'd have most of the bases covered.
        duaneb 11y ago
        Death by a thousand cuts! Pip is enough for anyone with google.
        tomc1985 11y ago
        This sounds crazy but we are actually in a situation where it is preferable to deploy python libraries via APT
- rinon 11y ago
  Hm, I wish my package manager understood pip. I always forget to upgrade pip along with my distro packages.
- fao_ 11y ago
  cough Arch User Repository, the one holy package management solution calling in cough ;)
  - asamarin 11y ago
    Indeed. Can't remember last time I installed a package using pip. This one, particularly, sits at https://aur.archlinux.org/packages/voltron-git/ https://aur.archlinux.org/packages/voltron-git/
- tacone 11y ago
  > With the current popularity of Python, it is only going to be a matter of time before apt / rpm / etc support working through it. LOL, not gonna happen. Ever.
- seanp2k2 11y ago
  Yep, just like what happened with CPAN and PEAR / PECL. Perl and PHP were / are popular too (so are ruby and node and go and Java and C++ and ...) and yet they still have their own independent package managers despite sometimes having very outdated versions of some modules in an distro's packaging system.
Manishearth 11y ago
Not everyone uses the Github "releases" feature, you can have a release without putting it on there. They've currently released it on pip.
- raimue 11y ago
  Not having a git tag for your release would be bad style. Actually, releases should always be tagged in order to make them reproducible. Everyone should be able to see what is in a release. Releasing software properly means that you actually care for this. Please do not just dump a git repo somewhere and expect distributions to pick up from there.

by raimue 11y ago

snarez 11y ago

Roritharr 11y ago
That was quick. https://github.com/snare/voltron/releases/tag/v0.1.1 https://github.com/snare/voltron/releases/tag/v0.1.1
snarez 11y ago
There was actually already a v0.1 release on PyPI and had been for some time, it just wasn't tagged on GitHub. The README says to use `pip install voltron`.

boxfire 11y ago

RTFM? Release versions are on pip. Unfortunately most distros think they have the one holy package management solution. pip IS a release and distribution system. With the current popularity of Python, it is only going to be a matter of time before apt / rpm / etc support working through it.

tomc1985 11y ago
It is trivial to generate a .deb from nearly any pip module... sudo apt-get install devscripts python-all-dev python-stdeb; cd path~to~pip; python setup.py --command-packages=stdeb.command bdist_deb
- duaneb 11y ago
  It's trivial to do a lot of niche catering and die by a thousand cuts. It's also trivial to install pip.
  - tomc1985 11y ago
    I'd hardly call debian and its derivatives 'niche', but whatever floats your boat...
    - duaneb 11y ago
      It's not niche in terms of OS deployment, perhaps, but a user's request for a `deb` file over traditional python packaging certainly is.
      - tomc1985 11y ago
        Perhaps, but this is to answer the call of 'os-native' packaging. I'd figure between msi+pkg+rpm+deb you'd have most of the bases covered.
        duaneb 11y ago
        Death by a thousand cuts! Pip is enough for anyone with google.
        tomc1985 11y ago
        This sounds crazy but we are actually in a situation where it is preferable to deploy python libraries via APT
rinon 11y ago
Hm, I wish my package manager understood pip. I always forget to upgrade pip along with my distro packages.
fao_ 11y ago
cough Arch User Repository, the one holy package management solution calling in cough ;)
- asamarin 11y ago
  Indeed. Can't remember last time I installed a package using pip. This one, particularly, sits at https://aur.archlinux.org/packages/voltron-git/ https://aur.archlinux.org/packages/voltron-git/
tacone 11y ago
> With the current popularity of Python, it is only going to be a matter of time before apt / rpm / etc support working through it. LOL, not gonna happen. Ever.
seanp2k2 11y ago
Yep, just like what happened with CPAN and PEAR / PECL. Perl and PHP were / are popular too (so are ruby and node and go and Java and C++ and ...) and yet they still have their own independent package managers despite sometimes having very outdated versions of some modules in an distro's packaging system.

Manishearth 11y ago

Not everyone uses the Github "releases" feature, you can have a release without putting it on there. They've currently released it on pip.

raimue 11y ago
Not having a git tag for your release would be bad style. Actually, releases should always be tagged in order to make them reproducible. Everyone should be able to see what is in a release. Releasing software properly means that you actually care for this. Please do not just dump a git repo somewhere and expect distributions to pick up from there.