Skip to content

Conversation

@jeckersb
Copy link
Collaborator

@jeckersb jeckersb commented Sep 2, 2025

Resolves: #1575
Signed-off-by: John Eckersberg [email protected]

@bootc-bot bootc-bot bot requested a review from cgwalters September 2, 2025 16:05
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly changes the creation of the storage symlink from an absolute path to a relative one, which improves the relocatability of the installed package. The use of realpath to compute the relative path for the final system (ignoring DESTDIR) is the correct approach. I've added a couple of suggestions to quote path variables to make the Makefile more robust against paths containing spaces.

@jeckersb jeckersb force-pushed the storage-relative-path branch from 64d42cf to 7099d1b Compare September 2, 2025 16:09
@jeckersb jeckersb force-pushed the storage-relative-path branch from 7099d1b to 5d49775 Compare September 2, 2025 20:30
@jeckersb jeckersb enabled auto-merge September 2, 2025 21:09
@jeckersb jeckersb merged commit 5be0261 into bootc-dev:main Sep 2, 2025
28 checks passed
@cgwalters
Copy link
Collaborator

Hm this seems to have tripped up a downstream rpm linter

image

Looking...

@cgwalters
Copy link
Collaborator

Hum maybe what we should do here actually is make it a mount point...

Or maybe we teach container-libs how to support AIS aliases

@cgwalters
Copy link
Collaborator

Nah I think this is all fine, it's just that it doesn't like dangling links, which I get...but hard to fix.

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.

RPM warning for absolute symlink

2 participants