This repository was archived by the owner on Jun 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 79
todo
Am Laher edited this page Apr 19, 2013
·
7 revisions
Contributions welcome via pull requests, thanks. Please use github 'issues' for discussion.
- Complete 'bintray' integration.
- support for 'source debs'.
- Improve .deb support (more config options. Support for changelog etc)
- 'exec' task (impetus for labels)
- 'labels' for tasks (so you can create multiple configs per task, e.g. exec:gen-sources and exec:gen-docs)
Below are change requirements with an unspecified priority. See existing issues for more immediate changes.
- 'launchpad' task. I guess this would depend on the 'source deb' task.
- add specific archive-zip and archive-tgz tasks
- -f (force) option
- Add option ldflags variable interpolation for main.VERSION variable name and other build flags. Use template for ldflags.
- Reintroduce static varable interpolation (write value into source code) as a task. Option for variable name.
- pre- & post-build scripts to run? pre-and-post for any task?
- Capability to run multiple configs at once? -c=a,b
- Bug: issue with config overriding. Empty strings do not currently override non-empty strings. Would involve more involved use of json and flagSet packages.
- Option to specify precise dir & name for a particular artifact?
- Permit unrecognised platforms (as Golang adds more)
- Respect +build flags inside file comments (just like 'go build' does)
- Much more error handling and potentially stop-on-error=true flag
- Refactoring: Utilise/copy from gotools source
- Meaningful godocs everywhere
- More Unit Tests!!
- Configurable 'downloads' page: name, format (e.g. markdown,html,ReST,jekyll-markdown),
Done: header/footer template? - Generate 'downloads overview' page (append each version's page as a relative link) ?
- Other Packaging (deb already done) e.g. source deb, .srpm & .rpm, .pkg? ... installer?
- Improve sanity check: automatically build target toolchain if missing? (need to work out detection mechanism)
- Improve sanity check: 'download golang source' option?
- Improve sanity check: warn about non-core libraries and binary dependencies?
- building .so/.dll shared libraries?
- Maybe someday: Build plugins (for OS-specific wizardry and stuff)? Pre- and post-processing scripts?
- Maybe someday: Investigate [forking and ?] hooking directly into the gotools source, instead of using os.exec. Fork would be required due to non-exported functions.
- Maybe someday: Use goroutines to speed up 'xc' (not toolchain because it recompiles host toolchain first)