3 ms·

I think parent is saying to use a package manager.

by krapht 5y ago

dagmx 5y ago
That would be the same issue though, just moved to a different spot
- nerdponx 5y ago
  Not necessarily. Package managers can cache things, especially if you're fetching the same version over and over. Also, separation of concerns is a good thing IMO.
  - howinteresting 5y ago
    Cargo etc also cache dependencies in a central location. "Separation of concerns" is ill-defined — you can use cargo as just a package manager, just a build system, or both. Most people use it as both but there are definitely places (e.g. bigcos) that use just one of the aspects of cargo.
- gspr 5y ago
  Separation of tasks. The build system builds. Another system (like a package manager, if you are so inclined, or not if not) manages packages.
  - howinteresting 5y ago
    Systems that combine the two generally let you use just one or the other. For example, cargo fetch just acts as the package manager. cargo build can be configured (through vendoring or just not using any external dependencies) to not perform any package management. What is missing is a modern cross-language, cross-platform package manager, I agree. But there are really good reasons for that, chief among them being that I don't think it's possible to define the scope of such a thing in a coherent fashion.
    - gspr 5y ago
      > Systems that combine the two generally let you use just one or the other. For example, cargo fetch just acts as the package manager. cargo build can be configured (through vendoring or just not using any external dependencies) to not perform any package management. Indeed, and I'm still highly skeptical. Learning Rust has been an amazingly rare sequence of "wow that's perfect" uttered from my mouth – except for Cargo. I couldn't disable the networking functionality of Cargo fast enough!
gspr 5y ago
Yes. Or not, if it's not suited for the task. But it seems insane to me to shoehorn this into the build system. I don't even understand why the latter should contain networking code at all.
- jcelerier 5y ago
  Let me guess, you also don't like that systemd is a system manager

I think parent is saying to use a package manager.

by krapht 5y ago

I think parent is saying to use a package manager.

dagmx 5y ago

That would be the same issue though, just moved to a different spot

nerdponx 5y ago
Not necessarily. Package managers can cache things, especially if you're fetching the same version over and over. Also, separation of concerns is a good thing IMO.
- howinteresting 5y ago
  Cargo etc also cache dependencies in a central location. "Separation of concerns" is ill-defined — you can use cargo as just a package manager, just a build system, or both. Most people use it as both but there are definitely places (e.g. bigcos) that use just one of the aspects of cargo.
gspr 5y ago
Separation of tasks. The build system builds. Another system (like a package manager, if you are so inclined, or not if not) manages packages.
- howinteresting 5y ago
  Systems that combine the two generally let you use just one or the other. For example, cargo fetch just acts as the package manager. cargo build can be configured (through vendoring or just not using any external dependencies) to not perform any package management. What is missing is a modern cross-language, cross-platform package manager, I agree. But there are really good reasons for that, chief among them being that I don't think it's possible to define the scope of such a thing in a coherent fashion.
  - gspr 5y ago
    > Systems that combine the two generally let you use just one or the other. For example, cargo fetch just acts as the package manager. cargo build can be configured (through vendoring or just not using any external dependencies) to not perform any package management. Indeed, and I'm still highly skeptical. Learning Rust has been an amazingly rare sequence of "wow that's perfect" uttered from my mouth – except for Cargo. I couldn't disable the networking functionality of Cargo fast enough!

gspr 5y ago

Yes. Or not, if it's not suited for the task. But it seems insane to me to shoehorn this into the build system. I don't even understand why the latter should contain networking code at all.

jcelerier 5y ago
Let me guess, you also don't like that systemd is a system manager