Libstuff is a library, in the system semantic (linux, same for windows). It may contain one crate, it should be still named after what it is in the system, but it is not properly speaking part of the rust semantic.
However alone it is almost useless, you need extra data to.locate, index, install, uninstall it,... and that what a package should be. Rust as two level: crates and package. Even if a concurrent packaging system "rustbetterpkg" can appear and do the same job differently without changing the rust language. Le 14 déc. 2013 05:28, "Liigo Zhuang" <[email protected]> a écrit : > 2013/12/14 Corey Richardson <[email protected]> > >> Packages don't really exist as a concept at all. Supposedly `rustpkg` >> deals with "packages" but in reality, it just deals with crates. >> >> And they're certainly not part of the module system. > > > 2013/12/14 György Andrasek <[email protected]> > >> On 12/14/2013 02:14 AM, Liigo Zhuang wrote: >> >>> What is the distinction of package and crate in Rust? >>> >> >> Crate is the compilation unit. Package is what you say it is, the Rust >> manual does not mention that word. > > > > There is an official tool called "rustpkg", and there is a attribute call > "pkgid", so you cann't just easily saying "there is no package" in rust. If > no package, why not using "rustcrate" and "crateid" for consistency? (I do > not think 'crate' is a good name, other languages tend to call it 'package' > or 'library'.) > > > >> On Fri, Dec 13, 2013 at 8:14 PM, Liigo Zhuang <[email protected]> >> wrote: >> > What is the distinction of package and crate in Rust? >> > >> > >> > 2013/12/14 Patrick Walton <[email protected]> >> >> >> >> On 12/13/13 4:56 PM, Liigo Zhuang wrote: >> >>> >> >>> "package" and "module", we only need one. Most other language only >> have >> >>> one. The more, the more complicate. >> >>> >> >>> libstd.so: What we call it? "library" "package" "crate"?? other >> language >> >>> usually call it "library". >> >>> std::io::fs: We call it "module", other language usually call it >> >>> "package" or "module". >> >>> >> >>> So, whatever we call it, package and module, we only need ONE of them, >> >>> and let another gone. >> >> >> >> >> >> .NET has a two-level distinction: assembly and namespace. >> >> >> >> C++ has a three-level distinction in practice—namespace, >> >> library/executable, and translation unit—although C++'s is somewhat >> >> different. >> >> >> >> OCaml has a two-level distinction: library and module. >> >> >> >> D has a two-level distinction as far as I can tell: library and module. >> >> >> >> Racket has a two-level distinction as far as I can tell: package and >> >> module. >> >> >> >> Patrick >> >> >> >> _______________________________________________ >> >> Rust-dev mailing list >> >> [email protected] >> >> https://mail.mozilla.org/listinfo/rust-dev >> > >> > >> > >> > >> > -- >> > by Liigo, http://blog.csdn.net/liigo/ >> > Google+ https://plus.google.com/105597640837742873343/ >> > >> > _______________________________________________ >> > Rust-dev mailing list >> > [email protected] >> > https://mail.mozilla.org/listinfo/rust-dev >> > >> > > > > -- > by *Liigo*, http://blog.csdn.net/liigo/ > Google+ https://plus.google.com/105597640837742873343/ > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
