https://pantsbuild.org/ logo
#general
Title
# general
l

little-easter-51691

07/27/2022, 1:21 PM
Hello, I am currently building an
archive
which should contain multiple build artefacts. Those artefacts are of type
pex_binary
and
python_distribution
(whl file for python). These artefacts are built when they are included in the
packages
field. Is there a way to control their location within the archive? For files, there is
relocated_files
.
b

bitter-ability-32190

07/27/2022, 2:03 PM
Not sure about
python_distribution
. Maybe we should add a similar field? @hundreds-father-404?
l

little-easter-51691

07/27/2022, 2:43 PM
Hm,
entry_points
in overrides of
pex_binaries
can control the location of the resulting pex file? In general it would be good to have a construct which moves built artefacts around. E.g. there might be a project which builds a whl on package and it is fine if it uses the default location
dist/<pants_naming_scheme
, but this project might be part of the build context of another project and then it would be good to be able to adapt the location of the artefacts, similar to relocate_files.
b

bitter-ability-32190

07/27/2022, 2:48 PM
Oh that's a bad link 😩 I meant the
output_path
field
l

little-easter-51691

07/27/2022, 4:10 PM
Thanks, yes this makes sense 🙂 .Having that option for
python_distribution
as well could be a first start. However it might be even better if the pathes could be specified within the build context of another project.
b

bitter-ability-32190

07/27/2022, 4:17 PM
Thats a very interesting take, and might fit in well with my upcoming proposal. I'll have to sit on it to think about how possible it'd be 🙂