Attention is currently required from: neels, pespin.

Patch set 4:Code-Review +1

View Change

1 comment:

• Patchset:

  • Patch Set #1:

    Personally, I don't see a need to spend time on moving code between repositories. […]

    It is a difficult question, and as neels has pointed out, one that has not really been properly resolved in our overall repository structure.

    • the libosmo-mgcp-client example is not applicable, as it really is only needed by code talking to osmo-mgw; likewise libosmo-gsup in osmo-hlr.git. Those are both fine, IMHO.
    • we do have other "strange" examples like osmo-stp being in libosmo-sccp.git. This is odd and should have been done properly from the start, as cleaning this up later means touching every bit of our infrastructure (from packaging recipes to OBS jobs, jenkins jobs and finally ansible playbooks, sysmoNITB stuff, etc.).

    So if we already know that libosmo-pfcp is [in the osmocom universe] only used internally by UPF or to talk to osmo-upf [or maybe some other upf] it is fine to keep it in osmo-upf.git. This reflects the MGCP-client, GSUP-client or even libgtp/ggsn situation.

To view, visit change 28245. To unsubscribe, or for help writing mail filters, visit settings.