Re: Poudriere: when fetching a package with porttree from a git source, the generation of logs is slow

On 2026/04/12 10:07, Mark Millard wrote:
> If I read the poudriere-devel code correctly (it is what I have
> installed), you have control of that through the likes of using:
> 
> # poudriere -s GIT_TREE_DIRTY_CHECK=no bulk . . .
> 
> "man poudriere" reports:
> 
>       -s var       Inherit the default for var from the environment.
> 
> 
>       -s var=value
>                    Set the default for var to the given value.
> 
> There are a bunch of defaults defined (including GIT_TREE_DIRTY_CHECK):
> 
> # grep ^: /usr/local/share/poudriere/common.sh | wc -l
>       106
> 
> (That may be an over or under count, but it gives an idea.)
> 
> For reference:
> 
> # grep GIT_TREE_DIRTY_CHECK /usr/local/share/poudriere/common.sh
> 	case "${GIT_TREE_DIRTY_CHECK-}" in
> : ${GIT_TREE_DIRTY_CHECK:=yes}
> 
> 
> and the code using it is:
> 
>          gghd_git_modified=no
>          msg_n "Inspecting ${git_dir} for modifications to git checkout..."
>          case "${GIT_TREE_DIRTY_CHECK-}" in
>          no)
>                  gghd_git_modified=unknown
>                  ;;
>          *)
>                  if git_tree_dirty "${git_dir:?}" "${inport}"; then
>                          gghd_git_modified=yes
>                  fi
>                  ;;
>          esac
>          echo " ${gghd_git_modified}"
>          setvar "${gghd_git_modified_var}" "${gghd_git_modified}"
> 
> So "no" avoids the get_tree_dirty activity.
> 
> I'm not aware of GIT_TREE_DIRTY_CHECK being publicly documented, so it
> may be more subject to change/removal than things that are documented.
> 
Thank you very much.
By already migrating to the -devel version, it has become possible to avoid the part where this issue occurs.
It has been changed to the extent that it cannot be backported, so unless we start using the -devel version, we have no choice but to wait for the official release.

Regards.