Re:What should go into the C++ standard library (2018)
by coldtea on Friday March 01, 2019 @04:15AM
(#19278992)
>Completely disagree, the system dependencies are my dependencies and whenever possible I want to be able to "make install" and have my dependencies update with the rest of my system.
You can disagree, but you'd be wrong in anything that a one-map-shop setting working on a single project, and willing to depend on the distro's (or third party distro package manager repos) versions of language libraries and frameworks.
>Entirely doable with existing package managers, just use the -root switch with dpkg or the --prefix switch with rpm or (or configure if you build from source). Typically I only want a small subset of version specific packages.
Typically this is a luxury that software shops with different projects (including older, already installed), different customers, etc., can't have.
>or python/perl/ruby, it used to be quite common to include packages from the OS repository, until they reinvented the wheel
Or until those languages weren't used merely by sys-admins and one-off scripts, but for large project development, and "include packages from the OS repository" wouldn't cut it anymore.
>For rust, that's why it's a joke as a "systems language".
Total non-seguitur. In fact, one of the main goals of C++ (as per the posted roadmap) is to add a package manager.
But the total non-seguitur that "Rust is a joke as a systems language" because it has cargo I think disqualifies anything else that can be said here.
You can disagree, but you'd be wrong in anything that a one-map-shop setting working on a single project, and willing to depend on the distro's (or third party distro package manager repos) versions of language libraries and frameworks.
>Entirely doable with existing package managers, just use the -root switch with dpkg or the --prefix switch with rpm or (or configure if you build from source). Typically I only want a small subset of version specific packages.
Typically this is a luxury that software shops with different projects (including older, already installed), different customers, etc., can't have.
>or python/perl/ruby, it used to be quite common to include packages from the OS repository, until they reinvented the wheel
Or until those languages weren't used merely by sys-admins and one-off scripts, but for large project development, and "include packages from the OS repository" wouldn't cut it anymore.
>For rust, that's why it's a joke as a "systems language".
Total non-seguitur. In fact, one of the main goals of C++ (as per the posted roadmap) is to add a package manager.
But the total non-seguitur that "Rust is a joke as a systems language" because it has cargo I think disqualifies anything else that can be said here.