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> |
||
|---|---|---|
| .. | ||
| per_namespace | ||
| share_image | ||
| arp_update_vars.j2 | ||
| buffers_config.j2 | ||
| cbf_config.j2 | ||
| config-chassisdb.service.j2 | ||
| config-setup.service.j2 | ||
| database.service.j2 | ||
| dhcp_relay.service.j2 | ||
| docker_image_ctl.j2 | ||
| gbsyncd-cisco.service.j2 | ||
| gbsyncd-credo.service.j2 | ||
| gbsyncd.service.j2 | ||
| iccpd.service.j2 | ||
| init_cfg.json.j2 | ||
| kube_cni.10-flannel.conflist | ||
| lldp.service.j2 | ||
| macsec.service.j2 | ||
| manifest.json.j2 | ||
| mgmt-framework.service.j2 | ||
| mgmt-framework.timer | ||
| mux.service.j2 | ||
| nat.service.j2 | ||
| organization_extensions.sh | ||
| packages.json.j2 | ||
| pde.service.j2 | ||
| pmon.service.j2 | ||
| qos_config.j2 | ||
| radv.service.j2 | ||
| restapi.service.j2 | ||
| sflow.service.j2 | ||
| snmp.service.j2 | ||
| snmp.timer | ||
| sonic_debian_extension.j2 | ||
| sonic_version.yml.j2 | ||
| sonic-delayed.target | ||
| sonic.target | ||
| swss_vars.j2 | ||
| tacacs-config.service | ||
| tacacs-config.timer | ||
| telemetry.service.j2 | ||
| telemetry.timer | ||
| updategraph.service.j2 | ||