Comment # 7 on bug 1090193 from Michael Andres

(In reply to Lukas Ocilka from comment #6)
> Is this an expected workflow? Do we have a better way?

I don't know in detail what AddOnProduct.SetRepoUrlAlias or Pkg.SourceCreate
are doing. pkg-bindings have their own source management on top of ZYPP.

It will mainly depend on where and why the unexpanded url is actually needed.

In theory it should be possible for pkg-bindings to place a (raw-)url argument
passed to SourceCreate in a zypp::RepoInfo class and let the RepoInfo hand out
'url()' or 'rawUrl()' as needed (i.e. let the RepoInfo do the replacement and
no need to exchange the url later).

If AddOnProduct.SetRepoUrlAlias requires an expanded url, you have to check why
and whether this can be somehow be changed..


OTOH Pkg.ExpandedUrl uses the zypp::RepoVariablesReplacedUrl class, which is
also used by the RepoInfo and which is expected to deliver back a correct
value. As long as pkg-bindings don't implement their own replacement, it should
be ok. It's just some overhead.