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

Paths: macros aren't expanded properly in sub-packages #16

Open
ermo opened this issue Sep 19, 2022 · 2 comments
Open

Paths: macros aren't expanded properly in sub-packages #16

ermo opened this issue Sep 19, 2022 · 2 comments

Comments

@ermo
Copy link
Member

ermo commented Sep 19, 2022

Thank you to @livingsilver94 for the bug report.

Repro:

packages :
    - "%(name)-staticlibs":
        summary: Static libraries
        description: Not really useful but for testing
        paths:
            - "%(libdir)/*.a"
@sunnyflunk
Copy link

What is the definition of %(libdir) for a emul32 build?

With multiple architectures this seems less helpful

@ikeycode ikeycode transferred this issue from another repository Mar 21, 2023
@ikeycode
Copy link
Member

I've been pondering this. How do you know which libdir to use in the context of yaml? its a really good point.
We can only expand non-architecture dependent, and at that point may as well just list the real paths. If the macros
change, so would the manifest, so its something we can trace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

4 participants