{"action":"created","issue":{"url":"https://api.github.com/repos/crosstool-ng/crosstool-ng/issues/1262","repository_url":"https://api.github.com/repos/crosstool-ng/crosstool-ng","labels_url":"https://api.github.com/repos/crosstool-ng/crosstool-ng/issues/1262/labels{/name}","comments_url":"https://api.github.com/repos/crosstool-ng/crosstool-ng/issues/1262/comments","events_url":"https://api.github.com/repos/crosstool-ng/crosstool-ng/issues/1262/events","html_url":"https://github.com/crosstool-ng/crosstool-ng/issues/1262","id":507128699,"node_id":"MDU6SXNzdWU1MDcxMjg2OTk=","number":1262,"title":"Feature request: build redistributable tarballs","user":{"login":"ali1234","id":651970,"node_id":"MDQ6VXNlcjY1MTk3MA==","avatar_url":"https://avatars2.githubusercontent.com/u/651970?v=4","gravatar_id":"","url":"https://api.github.com/users/ali1234","html_url":"https://github.com/ali1234","followers_url":"https://api.github.com/users/ali1234/followers","following_url":"https://api.github.com/users/ali1234/following{/other_user}","gists_url":"https://api.github.com/users/ali1234/gists{/gist_id}","starred_url":"https://api.github.com/users/ali1234/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ali1234/subscriptions","organizations_url":"https://api.github.com/users/ali1234/orgs","repos_url":"https://api.github.com/users/ali1234/repos","events_url":"https://api.github.com/users/ali1234/events{/privacy}","received_events_url":"https://api.github.com/users/ali1234/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-10-15T09:41:57Z","updated_at":"2019-10-16T07:59:14Z","closed_at":null,"author_association":"NONE","body":"It would be nice if there was an option to make redistributable tarballs of the built toolchain, similar to what Linaro ABE does. For example: https://releases.linaro.org/components/toolchain/binaries/7.4-2019.02/arm-linux-gnueabihf/\r\n\r\nI did a small proof-of-concept: https://github.com/ali1234/crosstool-ng/commit/e9cb71e5946bb7172cd3cd8d4590a31138f5f53a\r\n\r\nThis uses a similar approach to ABE - rsync to copy the toolchain into a directory named after the pkgversion, then tar it, then checksum it (ABE uses md5 but I used sha256).\r\n\r\nIf you are interested I would like to implement this properly, but there are some details that need to be worked out:\r\n\r\n1. What should the variables be called and what should the default values be?\r\n2. Which tarballs should be provided? ABE produces toolchain, sysroot, and runtime. I am not sure how the last two map to ct-ng, so I only did the toolchain.\r\n3. It would be useful to also copy source tarballs to the redist output. Currently ct-ng has one dir for source tarballs and it can have unneeded ones in it.\r\n4. How to make it so that \"make clean\" etc still works?\r\n5. Should this be a whole new build step?"},"comment":{"url":"https://api.github.com/repos/crosstool-ng/crosstool-ng/issues/comments/542575175","html_url":"https://github.com/crosstool-ng/crosstool-ng/issues/1262#issuecomment-542575175","issue_url":"https://api.github.com/repos/crosstool-ng/crosstool-ng/issues/1262","id":542575175,"node_id":"MDEyOklzc3VlQ29tbWVudDU0MjU3NTE3NQ==","user":{"login":"cpackham","id":155667,"node_id":"MDQ6VXNlcjE1NTY2Nw==","avatar_url":"https://avatars1.githubusercontent.com/u/155667?v=4","gravatar_id":"","url":"https://api.github.com/users/cpackham","html_url":"https://github.com/cpackham","followers_url":"https://api.github.com/users/cpackham/followers","following_url":"https://api.github.com/users/cpackham/following{/other_user}","gists_url":"https://api.github.com/users/cpackham/gists{/gist_id}","starred_url":"https://api.github.com/users/cpackham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cpackham/subscriptions","organizations_url":"https://api.github.com/users/cpackham/orgs","repos_url":"https://api.github.com/users/cpackham/repos","events_url":"https://api.github.com/users/cpackham/events{/privacy}","received_events_url":"https://api.github.com/users/cpackham/received_events","type":"User","site_admin":false},"created_at":"2019-10-16T07:59:14Z","updated_at":"2019-10-16T07:59:14Z","author_association":"CONTRIBUTOR","body":"At $dayjob we'd make use of this kind of feature. Currently we manually tar up the resulting toolchain so we can copy the result between containers.\r\n1. Naming things is hard. Defaulting to off is sensible for the first cut of this feature. We can change the default later if necessary. Others might have an opinion on the destination, but personally I'd go with directory `ct-ng build` was invoked.\r\n2. ct-ng is really just the toolchain so there's nothing for the other two\r\n3. I'd say no (or not without an option to omit them). The ct-ng configuration should allow you to recreate the toolchain. \r\n4. We don't really clean up the output toolchain with `ct-ng clean` so maybe do nothing. Alternatively if it does end up under the .build directory it will get cleaned up from there.\r\n5. To me it kind of feels wrong to have a step after \"finish\". But maybe that means just renaming the current \"finish\""}}
{"actor":{"display_login":"cpackham"}}