Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-tools / 636a6d42d6ae5186528a06bb324f0d5f9df0b928
commit636a6d42d6ae5186528a06bb324f0d5f9df0b928[log] [tgz]
authorJian Zhang <zhangjian.3032@bytedance.com>Fri Mar 15 00:29:16 2024 +0800
committerJian Zhang <zhangjian.3032@bytedance.com>Mon Mar 18 12:59:34 2024 +0800
tree22dd14839492500579d64ad60bd6f0cc52c816ac
parent96ebc4e78061da857cdb7278446b993fc483623d [diff]
ipkdbg: Add zstd support

The ipk using zstd to archive, add zstd support.

Since v0.5.0[0], the opkg support zstd.

[0]: https://git.yoctoproject.org/opkg/commit/?id=5dead41
~ git tag --contains=5dead41
```
v0.5.0
v0.6.0
v0.6.1
v0.6.2
v0.6.3
```

Change-Id: I92f19b703bb5e19bfb501b30ee4f2867f0fe781e
Signed-off-by: Jian Zhang <zhangjian.3032@bytedance.com>
1 file changed
tree: 22dd14839492500579d64ad60bd6f0cc52c816ac
  1. adcapp/
  2. altitude/
  3. autojson/
  4. bbdbg/
  5. bi2cp/
  6. cla-signers/
  7. dbus-pcap/
  8. dbus-vis/
  9. dbus_sensor_tester/
  10. dbusView/
  11. ddconvnotrunc/
  12. expectedJsonChecker/
  13. format-yaml/
  14. ipkdbg/
  15. netboot/
  16. openbmc-autobump/
  17. openbmctool/
  18. overlay/
  19. pldm/
  20. prepare-emmc-qemu/
  21. pretty-journal/
  22. pwmtachtool/
  23. reboot/
  24. reboot-ping-pong/
  25. rootfs_size/
  26. sensor_yaml_config/
  27. tof-voters/
  28. tracing/
  29. witherspoon-debug/
  30. .linter-ignore
  31. .shellcheck-ignore
  32. LICENSE
  33. OWNERS
  34. README.md
README.md

The OpenBMC Tools Collection

The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.

It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

If you're still with us

Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.

Sending patches

Please use gerrit for all patches to this repository:

Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.

What we will do once we have your patches

So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.

How you consume the repository

There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.