{"action":"created","issue":{"url":"https://api.github.com/repos/flame/blis/issues/210","repository_url":"https://api.github.com/repos/flame/blis","labels_url":"https://api.github.com/repos/flame/blis/issues/210/labels{/name}","comments_url":"https://api.github.com/repos/flame/blis/issues/210/comments","events_url":"https://api.github.com/repos/flame/blis/issues/210/events","html_url":"https://github.com/flame/blis/issues/210","id":325444075,"node_id":"MDU6SXNzdWUzMjU0NDQwNzU=","number":210,"title":"Getting BLIS into Ubuntu","user":{"login":"fgvanzee","id":5487570,"node_id":"MDQ6VXNlcjU0ODc1NzA=","avatar_url":"https://avatars1.githubusercontent.com/u/5487570?v=4","gravatar_id":"","url":"https://api.github.com/users/fgvanzee","html_url":"https://github.com/fgvanzee","followers_url":"https://api.github.com/users/fgvanzee/followers","following_url":"https://api.github.com/users/fgvanzee/following{/other_user}","gists_url":"https://api.github.com/users/fgvanzee/gists{/gist_id}","starred_url":"https://api.github.com/users/fgvanzee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgvanzee/subscriptions","organizations_url":"https://api.github.com/users/fgvanzee/orgs","repos_url":"https://api.github.com/users/fgvanzee/repos","events_url":"https://api.github.com/users/fgvanzee/events{/privacy}","received_events_url":"https://api.github.com/users/fgvanzee/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-05-22T20:07:44Z","updated_at":"2018-05-31T16:36:45Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Robert asked me recently, \"What would it take for BLIS to be incorporated into Ubuntu?\"\r\n\r\nSome light Googling lead me to understand that there are [four main repositories](https://help.ubuntu.com/community/Repositories) in Ubuntu: main, restricted, universe, multiverse. It sounds like we would be okay being in universe at least at first, especially if we need more time to prove ourselves suitable for main.\r\n\r\nI then found this [stackexchange thread](https://askubuntu.com/questions/16446/how-to-get-my-software-into-ubuntu) on the topic. The most up-voted response breaks down some of the options. It appears that getting into Debian is the most comprehensive choice (also indicated [here](http://packaging.ubuntu.com/html/packaging-new-software.html#submitting-for-inclusion)), as it would mean BLIS would be made available to users of both Linux distributions (Debian and Ubuntu). \r\n\r\nThanks to the work of [Nico Schlömer](https://launchpad.net/%7Enschloe/+archive/ubuntu/blis-devel), we already have someone involved with the project who knows how to create (and has created) PPA packages. The biggest hurdle, it seems, is to get a Debian Developer (DD) to [become our sponsor](https://wiki.debian.org/DebianMentorsFaq). This begins with a Request-for-Sponsor (RFS) bug report in Debian's bug-tracking system. (The RFS is like an ad designed to pique the interest of developer to become our sponsor.) But we are not supposed to submit the RFS until we have our source package ready for a potential sponsor to download/build/install. I think, thanks to Nico's work, we are basically there. (Care the comment, @nschloe?)\r\n\r\nNote that there is no guarantee that we will find a sponsor. There are a finite number of DDs, each with limited time and specific specializations/interests/preferences.\r\n\r\nAfter we get a sponsor, I think we will need this sponsor to upload any future revisions of the package. This is probably the most concerning to me aspect to me since BLIS has been undergoing relatively frequent updates.\r\n\r\nBottom line, this appears to be a non-trivial amount of work. So we should discuss/think carefully about if and when this would make sense for us.\r\n\r\nPlease comment, if you like."},"comment":{"url":"https://api.github.com/repos/flame/blis/issues/comments/393594660","html_url":"https://github.com/flame/blis/issues/210#issuecomment-393594660","issue_url":"https://api.github.com/repos/flame/blis/issues/210","id":393594660,"node_id":"MDEyOklzc3VlQ29tbWVudDM5MzU5NDY2MA==","user":{"login":"fgvanzee","id":5487570,"node_id":"MDQ6VXNlcjU0ODc1NzA=","avatar_url":"https://avatars1.githubusercontent.com/u/5487570?v=4","gravatar_id":"","url":"https://api.github.com/users/fgvanzee","html_url":"https://github.com/fgvanzee","followers_url":"https://api.github.com/users/fgvanzee/followers","following_url":"https://api.github.com/users/fgvanzee/following{/other_user}","gists_url":"https://api.github.com/users/fgvanzee/gists{/gist_id}","starred_url":"https://api.github.com/users/fgvanzee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgvanzee/subscriptions","organizations_url":"https://api.github.com/users/fgvanzee/orgs","repos_url":"https://api.github.com/users/fgvanzee/repos","events_url":"https://api.github.com/users/fgvanzee/events{/privacy}","received_events_url":"https://api.github.com/users/fgvanzee/received_events","type":"User","site_admin":false},"created_at":"2018-05-31T16:36:45Z","updated_at":"2018-05-31T16:36:45Z","author_association":"CONTRIBUTOR","body":"Thanks Dave, but I guess my question is why is it a convention that `libblas.so.3` use an `soname` of 3? Is it because BLAS did not change after the introduction of the level-3 operations? I can't help but notice that all of the other netlib libraries seem to use an `soname` of 3 as well. Maybe it has to do with the current major version number of LAPACK? (It's okay if you don't know the answer.)"}}
{"actor":{"display_login":"fgvanzee"}}