2ef97bb5df
- Why I did it In case an app.ext requires a dependency syncd^1.0.0, the RPC version of syncd will not satisfy this constraint, since 1.0.0-rpc < 1.0.0. This is not correct to put 'rpc' as a prerelease identifier. Instead put 'rpc' as build metadata in the version: 1.0.0+rpc which satisfies the constraint ^1.0.0. - How I did it Changed the way how to version in RPC and DBG images are constructed. - How to verify it Install app.ext with syncd^1.0.0 dependency on a switch with RPC syncd docker. Signed-off-by: Stepan Blyshchak <stepanb@nvidia.com> |
||
|---|---|---|
| .. | ||
| cavm_platform_modules | ||
| cavm_sdk | ||
| docker-saiserver-cavm | ||
| docker-syncd-cavm | ||
| docker-syncd-cavm-rpc | ||
| cavm-platform-modules.mk | ||
| cavm-sai.mk | ||
| cavm-xpnet.mk | ||
| docker-syncd-cavm-rpc.mk | ||
| docker-syncd-cavm.mk | ||
| libsaithrift-dev.mk | ||
| one-image.mk | ||
| platform.conf | ||
| rules.mk | ||