diff options
| author | Daniel Mueller <deso@posteo.net> | 2020-04-04 14:39:19 -0700 |
|---|---|---|
| committer | Daniel Mueller <deso@posteo.net> | 2020-04-04 14:39:19 -0700 |
| commit | d0d9683df8398696147e7ee1fcffb2e4e957008c (patch) | |
| tree | 4baa76712a76f4d072ee3936c07956580b230820 /libc/.github | |
| parent | 203e691f46d591a2cc8acdfd850fa9f5b0fb8a98 (diff) | |
| download | nitrocli-d0d9683df8398696147e7ee1fcffb2e4e957008c.tar.gz nitrocli-d0d9683df8398696147e7ee1fcffb2e4e957008c.tar.bz2 | |
Remove vendored dependencies
While it appears that by now we actually can get successful builds
without Cargo insisting on Internet access by virtue of using the
--frozen flag, maintaining vendored dependencies is somewhat of a pain
point. This state will also get worse with upcoming changes that replace
argparse in favor of structopt and pull in a slew of new dependencies by
doing so. Then there is also the repository structure aspect, which is
non-standard due to the way we vendor dependencies and a potential
source of confusion.
In order to fix these problems, this change removes all the vendored
dependencies we have.
Delete subrepo argparse/:argparse
Delete subrepo base32/:base32
Delete subrepo cc/:cc
Delete subrepo cfg-if/:cfg-if
Delete subrepo getrandom/:getrandom
Delete subrepo lazy-static/:lazy-static
Delete subrepo libc/:libc
Delete subrepo nitrokey-sys/:nitrokey-sys
Delete subrepo nitrokey/:nitrokey
Delete subrepo rand/:rand
Diffstat (limited to 'libc/.github')
| -rw-r--r-- | libc/.github/issue_template.md | 24 |
1 files changed, 0 insertions, 24 deletions
diff --git a/libc/.github/issue_template.md b/libc/.github/issue_template.md deleted file mode 100644 index 435bf35..0000000 --- a/libc/.github/issue_template.md +++ /dev/null @@ -1,24 +0,0 @@ -<!-- -**Help us help you.** - -If you are reporting a bug, include: - -* a Minimum Working Example without any dependencies (except libc) that shows - the issue and ideally reproduces in the Rust playground -* the target triple - libc supports many targets and many APIs -* instructions to reproduce, logs (e.g. build logs, links to Travis-CI logs, - uploads to github gists, etc.). - -If you are requesting a new API, include: - -* the target triple -* link to the documentation of the API showing the type signatures, how to use - it, etc. - -In general, just please consider that the people who can help you are all very -busy, they will be helping you in their free time, there are a lot of people in -need of help so they need to prioritize to which issues they devote their free -time, etc. So try to give most of the information upfront, be concise, show -small self-contained examples (nobody has time to create a new cargo project, -set up dependencies,...), etc. Help us help you. ---> |