Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Url varexpand issues #497

Draft
wants to merge 9 commits into
base: master
Choose a base branch
from
Draft

Conversation

mlandres
Copy link
Member

@mlandres mlandres marked this pull request as draft November 17, 2023 15:32
@mlandres mlandres force-pushed the ma-1217192-URL_varexpand_issues branch 9 times, most recently from c73a80b to dc1a9c0 Compare November 29, 2023 13:59
@mlandres mlandres force-pushed the ma-1217192-URL_varexpand_issues branch from dc1a9c0 to 6b31a68 Compare November 29, 2023 14:35
@mlandres
Copy link
Member Author

Introducing the zypp-rawurl: schema to transport unexpanded strings parsed from a .repo/.service file into the RepoInfo (which is able to actually replace the variables) has it's obstacles. We need to resolve all kinds of Url manipulation which were formerly performed on the unexpanded Url (based on the assumption they will be still valid after variable expansion).

Now we use the zypp-rawurl: query part to build a kind of todo list to be performed on the Url after variable expansion.

@mlandres mlandres force-pushed the ma-1217192-URL_varexpand_issues branch from 6b31a68 to ae2cc75 Compare November 29, 2023 15:00
As a regex is used anyway there's also no need for substring actions.
…definitions

An incomplete variable definition is to be expanded literally. It should
produce the same result as if the the introducing '$' was escaped.
…o variables

The schema is used internally to wrap raw strings with unexpanded
repo variables into type Url. The raw string is stored in the Url's
fragment because it does not necessarily form a valid Url before it
got expanded.
Repo/Service file: Full support for using repo variables in URLs (bsc#1217192)

With a libzypp providing 'libzypp(repovarexpand) >= 1.2' the use of
repo variables in URLs is no longer restricted to the host and path
component of an URL, nor must the not-expanded string form a valid URL.
@mlandres mlandres force-pushed the ma-1217192-URL_varexpand_issues branch from ae2cc75 to a7d1a12 Compare December 15, 2023 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant