4 ms·

apt is not cross-platform.

lucb1e 10y ago
OS X, BSD, Android, Fedora, etc. users will just have to use their respective package managers, or use the second option if there is none (downloading the source to a subdirectory). Python code will not run without a platform-specific interpreter anyway.
- pvg 10y ago
  Those package managers would then have to know a lot about the specific needs of each language runtime they support. They don't and shouldn't. The alternative - each runtime has its own canonical package manager means you get parallel package systems and duplicated effort which is unfortunate. On the other hand, they actually work unlike, say, 'apt for python packages'.
mhurron 10y ago
apt also installs packages globally to the system and not every python package exists as a deb package.
- dozzie 10y ago
  Are you from the crowd that thinks that DEB packages only grow on preselected trees and people can't build a DEB themselves for what they need?
  - mhurron 10y ago
    If I have to build a deb to install something, I might as well just save myself the time and use pip. The convenience of a package manager goes away when you have to package everything yourself before you can use it. At that point saying 'why doesn't everyone just use apt-get' is the same as saying 'why doesn't everyone just configure ; make ; make install.' I also don't use Debian.
    - dozzie 10y ago
      > The convenience of a package manager goes away when you have to package everything yourself before you can use it. Far from it. You get repeatable builds and deployments, much easier and faster setup of development environment (GCC and -devel packages and foreign-language tools pulled in automatically), and you don't make intractable mess on your servers, which allows you to use much wider range of tools than architecturally broken Ansible/Salt. > I also don't use Debian. Irrelevant. Every Linux distribution and most other unix operating systems use some package manager, most of which in turn are more or less equivalent to APT.

OS X, BSD, Android, Fedora, etc. users will just have to use their respective package managers, or use the second option if there is none (downloading the source to a subdirectory). Python code will not run without a platform-specific interpreter anyway.

pvg 10y ago
Those package managers would then have to know a lot about the specific needs of each language runtime they support. They don't and shouldn't. The alternative - each runtime has its own canonical package manager means you get parallel package systems and duplicated effort which is unfortunate. On the other hand, they actually work unlike, say, 'apt for python packages'.

mhurron 10y ago

apt also installs packages globally to the system and not every python package exists as a deb package.

dozzie 10y ago
Are you from the crowd that thinks that DEB packages only grow on preselected trees and people can't build a DEB themselves for what they need?
- mhurron 10y ago
  If I have to build a deb to install something, I might as well just save myself the time and use pip. The convenience of a package manager goes away when you have to package everything yourself before you can use it. At that point saying 'why doesn't everyone just use apt-get' is the same as saying 'why doesn't everyone just configure ; make ; make install.' I also don't use Debian.
  - dozzie 10y ago
    > The convenience of a package manager goes away when you have to package everything yourself before you can use it. Far from it. You get repeatable builds and deployments, much easier and faster setup of development environment (GCC and -devel packages and foreign-language tools pulled in automatically), and you don't make intractable mess on your servers, which allows you to use much wider range of tools than architecturally broken Ansible/Salt. > I also don't use Debian. Irrelevant. Every Linux distribution and most other unix operating systems use some package manager, most of which in turn are more or less equivalent to APT.