| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| add opencode | 9 months ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |
| fix: ship both architecture source sets in the SRPM Source2/Source3 derived their file names from the build architecture (%{_target_cpu}, %{nodejs_arch}), so a single spec parse resolved exactly one variant and the SRPM only carried that architecture's tarballs. Rebuilding such an SRPM for the other architecture resolved %{SOURCE2} to a file the package did not contain, so an x86_64 SRPM could not be rebuilt for aarch64. Declare both variants as separate fixed-name sources and select the matching pair at build time with %ifarch: Source2/3 opencode-deps-{x86_64,aarch64}-%{version}.tar.xz, Source4/5 node-v%{nodejs_version}-linux-{x64,arm64}.tar.xz, Source6 opencode-assets-%{version}.tar.gz. Verified with rpmbuild -bs on the openEuler 24.03 x86_64 and aarch64 build VMs: the SRPM now contains both opencode-deps tarballs and both Node.js tarballs. Release: 1 -> 2. | 1 month ago |
| chore: sync upstream opencode release v1.17.13 Signed-off-by: Hongyu Shi <shywzt@iCloud.com> | 4 months ago |