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

RFE: support substitution in environment.environment #1402

Open
smoser opened this issue Jul 23, 2024 · 0 comments
Open

RFE: support substitution in environment.environment #1402

smoser opened this issue Jul 23, 2024 · 0 comments

Comments

@smoser
Copy link
Contributor

smoser commented Jul 23, 2024

I have a situation where I would like to put SETUPTOOLS_SCM_PRETEND_VERSION=${{package.version}} into the build environment.

I want to do:

environment:
  environment:
    SETUPTOOLS_SCM_PRETEND_VERSION: ${{package.version}}
    OTHER: "other is ${{vars.VARS}}"

The second 'OTHER' there i just put there. I think it is reasonable to support substitution within a string rather than only supporting the entire string. but I do not want to request shell-like behavior or expansion.

I also would lke to request that work within a 'range' section like seen here.

smoser added a commit to smoser/wolfi-os that referenced this issue Oct 8, 2024
A couple things here:
1. fix FTBFS state that apache-arrow was currently in.

  * need zstd-static because:

       CMake Error at /usr/lib64/cmake/zstd/zstdTargets.cmake:107 (message):
         The imported target "zstd::libzstd_static" references the file
            "/usr/lib/libzstd.a" uses=cmake/configure
         but this file does not exist.  Possible reasons include:

2. cherry-pick a patch (from 2016) to rapidjson that allows a user of it
   (apache-arrow) to build with gcc-14.

3. Add environment variables to build so the python build modules
   have access.  I had hoped to localize these or use substitution
   in the environment block, but that is not supported.

   chainguard-dev/melange#1548
   chainguard-dev/melange#1402

4. drop unnecessary runtime dependency from libarrow to libarrow.

5. remove pyarrow.

6. bump the epoch on apache-arrow to 3 to be newer than pyarrow was.
smoser added a commit to smoser/wolfi-os that referenced this issue Oct 8, 2024
A couple things here:
1. fix FTBFS state that apache-arrow was currently in.

  * need zstd-static because:

       CMake Error at /usr/lib64/cmake/zstd/zstdTargets.cmake:107 (message):
         The imported target "zstd::libzstd_static" references the file
            "/usr/lib/libzstd.a" uses=cmake/configure
         but this file does not exist.  Possible reasons include:

2. cherry-pick a patch (from 2016) to rapidjson that allows a user of it
   (apache-arrow) to build with gcc-14.

3. Add environment variables to build so the python build modules
   have access.  I had hoped to localize these or use substitution
   in the environment block, but that is not supported.

   chainguard-dev/melange#1548
   chainguard-dev/melange#1402

4. drop unnecessary runtime dependency from libarrow to libarrow.

5. remove pyarrow.

6. bump the epoch on apache-arrow to 3 to be newer than pyarrow was.
smoser added a commit to smoser/wolfi-os that referenced this issue Oct 8, 2024
A couple things here:
1. fix FTBFS state that apache-arrow was currently in.

  * need zstd-static because:

       CMake Error at /usr/lib64/cmake/zstd/zstdTargets.cmake:107 (message):
         The imported target "zstd::libzstd_static" references the file
            "/usr/lib/libzstd.a" uses=cmake/configure
         but this file does not exist.  Possible reasons include:

2. cherry-pick a patch (from 2016) to rapidjson that allows a user of it
   (apache-arrow) to build with gcc-14.

3. Add environment variables to build so the python build modules
   have access.  I had hoped to localize these or use substitution
   in the environment block, but that is not supported.

   chainguard-dev/melange#1548
   chainguard-dev/melange#1402

4. drop unnecessary runtime dependency from libarrow to libarrow.

5. remove pyarrow.

6. bump the epoch on apache-arrow to 3 to be newer than pyarrow was.
smoser added a commit to wolfi-dev/os that referenced this issue Oct 8, 2024
…30285)

A couple things here:
1. fix FTBFS state that apache-arrow was currently in.

  * need zstd-static because:

CMake Error at /usr/lib64/cmake/zstd/zstdTargets.cmake:107 (message):
         The imported target "zstd::libzstd_static" references the file
            "/usr/lib/libzstd.a" uses=cmake/configure
         but this file does not exist.  Possible reasons include:

2. cherry-pick a patch (from 2016) to rapidjson that allows a user of it
   (apache-arrow) to build with gcc-14.

3. Add environment variables to build so the python build modules
   have access.  I had hoped to localize these or use substitution
   in the environment block, but that is not supported.

   chainguard-dev/melange#1548
   chainguard-dev/melange#1402

4. drop unnecessary runtime dependency from libarrow to libarrow.

5. remove pyarrow.

6. bump the epoch on apache-arrow to 3 to be newer than pyarrow was.

7. provide multiple versions of the python modules, and make them
provide 'pyarrow' for backwards compat.
gdonval pushed a commit to gdonval/wolfi-os that referenced this issue Oct 9, 2024
…olfi-dev#30285)

A couple things here:
1. fix FTBFS state that apache-arrow was currently in.

  * need zstd-static because:

CMake Error at /usr/lib64/cmake/zstd/zstdTargets.cmake:107 (message):
         The imported target "zstd::libzstd_static" references the file
            "/usr/lib/libzstd.a" uses=cmake/configure
         but this file does not exist.  Possible reasons include:

2. cherry-pick a patch (from 2016) to rapidjson that allows a user of it
   (apache-arrow) to build with gcc-14.

3. Add environment variables to build so the python build modules
   have access.  I had hoped to localize these or use substitution
   in the environment block, but that is not supported.

   chainguard-dev/melange#1548
   chainguard-dev/melange#1402

4. drop unnecessary runtime dependency from libarrow to libarrow.

5. remove pyarrow.

6. bump the epoch on apache-arrow to 3 to be newer than pyarrow was.

7. provide multiple versions of the python modules, and make them
provide 'pyarrow' for backwards compat.
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

No branches or pull requests

1 participant