{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/d0ce8e171d43e20591074a66e9ff7ae6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d0ce8e171d43e20591074a66e9ff7ae6","url":"https://api.github.com/users/brson","login":"brson","id":147214},"milestone":null,"assignee":null,"updated_at":"2011-11-09T03:26:28Z","labels":[{"name":"cleanup","color":"7dfae7","url":"https://api.github.com/repos/graydon/rust/labels/cleanup"},{"name":"feature","color":"d912e0","url":"https://api.github.com/repos/graydon/rust/labels/feature"},{"name":"unassigned","color":"02e10c","url":"https://api.github.com/repos/graydon/rust/labels/unassigned"}],"comments":2,"closed_at":null,"url":"https://api.github.com/repos/graydon/rust/issues/1157","body":"In 16dad84f7b2f173db012dda2e77b08ccb423391f we made the crate search based purely on metadata, so that we could rename libstd to libruststd.\r\n\r\nAs graydon pointed out, we are supposed to name our libraries `lib[name]-[hash]-[version].so`, so there's no way that libstd should cause a name collision.\r\n\r\nImplement this naming convention, revert the above change and rename libruststd back to libstd.","html_url":"https://github.com/graydon/rust/issues/1157","title":"Implement versioned library naming and rename libruststd back to libstd","number":1157,"id":2176960,"created_at":"2011-11-08T17:33:28Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/d0ce8e171d43e20591074a66e9ff7ae6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d0ce8e171d43e20591074a66e9ff7ae6","url":"https://api.github.com/users/brson","login":"brson","id":147214},"updated_at":"2011-11-09T03:26:28Z","url":"https://api.github.com/repos/graydon/rust/issues/comments/2677094","body":"There are some very detailed comments about how Rust versioning is supposed to work in src/comp/back/link.rs that you should read.\r\n\r\nI don't know anything about sonames so can't answer the first two questions (my guess is the answer to both is no - we're creating our own, platform-agnostic versioning mechanism). Maybe graydon has an opinion.\r\n\r\nAs to the last question, we don't need to verify the hash. This hash is just a hash of the exported metadata (everything in the #[link] attribute), and used to help differentiate the filename from other builds of the same library. I don't think we're using it for any security properties.\r\n\r\nI'm a bit worried about how this will impact the build system since we won't be able to know the names of the libraries we're producing.","id":2677094,"created_at":"2011-11-09T03:26:28Z"}}