On Sat, Feb 1, 2014 at 4:28 PM, Vladimir Matveev > > Well, it seems that working for a long time with a code targeting virtual > machines is corrupting :) I completely forgot about different models of > compilation. I see your point. But I think that developing and distributing > should be considered separately. Package manager for developers should be a > part of language infrastructure (like rustpkg is now for Rust and, for > example, > go tool for Go language or cabal for Haskell). This package manager allows > flexible management of Rust libraries and their dependencies, and it should be > integrated with the build system (or *be* this build system). It is used by > developers to create applications and libraries and by maintainers to prepare > these applications and libraries for integration with the distribution system > for end users.
How will it handle external dependencies? > Package manager for general users (I'll call it system package manager), > however, depends on the OS, and it is maintainer's task to determine correct > dependencies for each package. Rust package manager should not depend in any > way on the system package manager and its packages, because each system has > its > own package manager, and it is just impossible to support them all. Rust also > should not force usage of concrete user-level package manager (like 0install, > for example), because this means additional unrelated software on the user > installation. I don't understand this. A package manager specific to Rust is additional software, just like 0install. 0install has full support for installing dependencies via the system package manager on many systems if desired. http://0install.net/distribution-integration.html _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
