[
https://issues.apache.org/jira/browse/TC-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087442#comment-16087442
]
ASF GitHub Bot commented on TC-192:
-----------------------------------
Github user elsloo commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/731
Hey @rguiliani, thanks for the PR. When the two Traffic Monitor RPMs are
built, we will end up with an RPM with `_go` in its name, which will be
included in the version. Do you know whether this resulting RPM can still be
installed via `yum install traffic_monitor`?
We must ensure that our installation and upgrade path is still valid, as we
have existing installations using the non-`_go` named version of the RPM, and
we need to be able to run `yum upgrade traffic_monitor` to get to the next
version.
Based on what I know of the spec file, I *think* this will work, but I
would like confirmation.
> Java TM and Go TM get build with exact same RPM Name
> ----------------------------------------------------
>
> Key: TC-192
> URL: https://issues.apache.org/jira/browse/TC-192
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Monitor, Traffic Monitor (golang)
> Affects Versions: 2.1.0, 2.0.0
> Reporter: David Neuman
> Labels: build, gotm, javatm
>
> When building Traffic Control, goTM and javaTM get build with the exact same
> rpm name. This means that if you are building all projects you only get one
> TM RPM and its whichever one built last. The names should be updated so that
> they are not the same.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
