Comment # 12 on bug 962599 from Dominique Leuenberger

(In reply to Matwey Kornilov from comment #11)
> This won't help packages which are already in d:l:e. As soon as Factory will
> have package erlang-rebar, they will fetch it instead of local
> erlang-rebar-obs. Aren't they?

Yes, they would indeed (and I see the most important part you care for is the
fact that rebar-obs does not rely on networking).

Then I'd actually do it like this (which is a bit of work, but would be clean)

in erlang-rebar-obs:
Provides: erlang-rebar(nonet) = %{version}

in erlang-retest:
BuildRequires: erlang-rebar(nonet)

in erlang-rebar:
BuildRequires: erlang-retest (as is IIRC)

Then all packages would have to specify that the way want an erlang-rebar with
the capability to use nonet.

An even cleaner solution would be similar to what ruby does: prefer if local is
found and use net otherwise.. in OBS we can provide the local stuff my means of
buildrequires and on the end user machines they can still go net if they want
to.

This would probably eliminate the need for the -obs package alltogether

Or I misunderstand what the point is that is actually trying to be solved