pip: Recommend pybuild-deps package for generating requirements-build.txt

[slimreaper35]

Maintainers will complete the following section

• Commit messages are descriptive enough
• Code coverage from testing does not decrease and new code is covered
• Docs updated (if applicable)
• Docs links in the code are still valid (if docs were updated)

Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:

• approve GitHub Actions workflows by clicking a button
• approve the Red Hat Trusted App Pipeline container build by commenting /ok-to-test
  (as is the standard for Pipelines as Code)

[eskultety]

The PR lacks context for this change, e.g. so we're moving some script from other repo to our repo, why? What's the motivation behind the change, what is it improving/addressing? Otherwise LGTM.

[chmeliik]

Is it time to start recommending https://github.com/bruno-fs/pybuild-deps instead?

[brunoapimentel]

Is it time to start recommending https://github.com/bruno-fs/pybuild-deps instead?

Yes, I pushed for this at the time you filed those issues. We can revisit this now.

[slimreaper35]

The PR lacks context for this change, e.g. so we're moving some script from other repo to our repo, why? What's the motivation behind the change, what is it improving/addressing? Otherwise LGTM.

I thought, that when we break the relationship with Cachito completely and update all the references, we should move the script for generating build dependencies here. I don't know in what shape is https://github.com/bruno-fs/pybuild-deps but we can for example have this as an alternative option mentioned in the docs.

[brunoapimentel]

I thought, that when we break the relationship with Cachito completely and update all the references, we should move the script for generating build dependencies here. I don't know in what shape is https://github.com/bruno-fs/pybuild-deps but we can for example have this as an alternative option mentioned in the docs.

I would rather just stop referecing the script at all and simply point to pybuild-deps, as it is a more robust and efficient solution.

(btw, the developer has already asked us to move pybuild-deps under our organization, so we in case we decide to go that way, we would become the maintainers of this project, making it more "official")

[slimreaper35]

I would rather just stop referecing the script at all and simply point to pybuild-deps, as it is a more robust and efficient solution.
(btw, the developer has already asked us to move pybuild-deps under our organization, so we in case we decide to go that way, we would become the maintainers of this project, making it more "official")

Do you want me to do it in this PR? Or wait until we move our repo under a new organization and decide on pybuild-deps location?

[brunoapimentel]

Do you want me to do it in this PR? Or wait until we move our repo under a new organization and decide on pybuild-deps location?

I slightly preferer doing it now rather than moving the script to this repo and replacing it with pybuild-deps later. Wdyt @eskultety @a-ovchinnikov? Otherwise, let's follow up this PR as is, I'd be fine with it too.

[slimreaper35]

So let's do it here. It is a simple change in the docs. Does not make sense to "temporarily" merge those two commits.

[eskultety]

Do you want me to do it in this PR? Or wait until we move our repo under a new organization and decide on pybuild-deps location?

I slightly preferer doing it now rather than moving the script to this repo and replacing it with pybuild-deps later. Wdyt @eskultety @a-ovchinnikov? Otherwise, let's follow up this PR as is, I'd be fine with it too.

Can you be more specific on what "prefer doing it now" encompasses? Do you mean ONLY referencing that external project/script in our docs OR move their whole repo under this org and become maintainers straight away? Because I am totally on board with the former while I may need a little while to think about the latter as I've never seen the project in question.

[brunoapimentel]

Can you be more specific on what "prefer doing it now" encompasses? Do you mean ONLY referencing that external project/script in our docs OR move their whole repo under this org and become maintainers straight away? Because I am totally on board with the former while I may need a little while to think about the latter as I've never seen the project in question.

Only referencing the external project (pybuild-deps) and stop referencing the old script altogether. The reasoning is that pybuild-deps is a more robust solution, with tests and more readable code, it has a much faster resolution time and it solves problems such as conflicting versions for build dependencies that the current script does not.

The latter (adopting the project) is something we'll need to carefully consider, but it is out of scope for this PR (I only mentioned it because I wanted to show that this is not just a random external project)

[eskultety]

Can you be more specific on what "prefer doing it now" encompasses? Do you mean ONLY referencing that external project/script in our docs OR move their whole repo under this org and become maintainers straight away? Because I am totally on board with the former while I may need a little while to think about the latter as I've never seen the project in question.

Only referencing the external project (pybuild-deps) and stop referencing the old script altogether. The reasoning is that pybuild-deps is a more robust solution, with tests and more readable code, it has a much faster resolution time and it solves problems such as conflicting versions for build dependencies that the current script does not.

The latter (adopting the project) is something we'll need to carefully consider, but it is out of scope for this PR (I only mentioned it because I wanted to show that this is not just a random external project)

Thanks for clarifying - ACK to that in that case.