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

Explain custom chroots #3567

Merged
merged 1 commit into from
Jan 7, 2025
Merged

Explain custom chroots #3567

merged 1 commit into from
Jan 7, 2025

Conversation

FrostyX
Copy link
Member

@FrostyX FrostyX commented Jan 2, 2025

Fix #3226

to the project owners to enable the desired chroots for their projects.

In some advanced cases, it can happen that an appropriate chroot isn't
available. The distribution might me too niche, the chroot config might enable
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
available. The distribution might me too niche, the chroot config might enable
available. The distribution might be too niche, the chroot config might enable


In a hypothetical scenario where ``fedora-rawhide-x86_64`` chroot doesn't exist,
here is how to re-create it through a custom chroot. First, go to your project
settings and enable ``custom-1-x86_64`` chroot. Then go the project settings
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
settings and enable ``custom-1-x86_64`` chroot. Then go the project settings
settings and enable ``custom-1-x86_64`` chroot. Then go to the project settings

https://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/

And lastly, specify the list of packages that should be installed to the minimal
buildroot before an RPM package is attempted to be built. Groups names are
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
buildroot before an RPM package is attempted to be built. Groups names are
buildroot before an RPM package is attempted to be built. Group names are

@build

You won't ever need to do this for Fedora Rawhide, but you can use this exact
approach for any distribution that is not officially supported.
Copy link
Member

@praiskup praiskup Jan 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can imagine a situation when someone requires even more limited set of packages in minimal Rawhide build root... I'd probably relax the "you won't ever need" to something like "you likely won't need" :)

@praiskup
Copy link
Member

praiskup commented Jan 6, 2025

Good write up, thanks.

@FrostyX
Copy link
Member Author

FrostyX commented Jan 6, 2025

So many typos, thank you for the review. Updated, PTAL.

Copy link
Member

@xsuchy xsuchy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Member

@praiskup praiskup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@praiskup praiskup merged commit e69b8b4 into fedora-copr:main Jan 7, 2025
6 checks passed
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

Successfully merging this pull request may close these issues.

Document how to use custom-1-* chroots
4 participants