Documentation/build_qubes_packages.md: add procedure for building qub… #7
Conversation
…es packages Signed-off-by: Michał Żygowski <[email protected]> Signed-off-by: Tomasz Żyjewski <[email protected]>
| [getfedora](https://getfedora.org/en/workstation/download/), later the Fedora | ||
| 37 will probable be stored in | ||
| [archive](https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/). | ||
|
|
| @@ -0,0 +1,320 @@ | |||
| # Qubes OS Packages | |||
There was a problem hiding this comment.
How this documentation can be found?
- there is not mention of it in README
- maybe reference in TrenchBoot Documentation which is published https://trenchboot.org/ should be considered?
TrenchBoot as Qubes OS AEM should gain more visibility on TrenchBoot website.
Also whenever we have some progress to share it is worthy to try engage community on #trenchboot channel at OSFW slack (and in Dasharo Matrix Space).
| [Qubes builder](https://www.qubes-os.org/doc/qubes-builder/) can be used to | ||
| prepare new ISO image but also to build customized packages. To do the latter | ||
| we will need PC with Fedora installed (may be any version as builder prepare | ||
| fc32 chroot itself). |
There was a problem hiding this comment.
This paragraph sound more like requirements. Also I wonder about new qubes-builder which was announced at Qubes OS Summit, are we using it, and if not then the question is why?
There was a problem hiding this comment.
AFAIK new builder should not be OS-dependent because it leverage containers
There was a problem hiding this comment.
dunno which one was announced at summit, but we used one pointed in documentation https://www.qubes-os.org/doc/qubes-builder/ which says In order to use it, you should use an rpm-based distro, like Fedora
There was a problem hiding this comment.
@TomaszAIR I guess there are plans to enable builder for other OSes (docker-based solution IIRC). I tried to test it during Qubes OS summit, but had issues with it: https://github.com/QubesOS/qubes-builderv2
Anyway, if for now we use v1 which is recommended it is ok, but in long run I would appreciate to support also Debian-based environment which many community members use.
| qubes-src/grub2/pkgs/dom0-fc32/x86_64/grub2-tools-extra-debuginfo-2.06-0.1.fc32.x86_64.rpm | ||
| qubes-src/grub2/pkgs/dom0-fc32/x86_64/grub2-tools-minimal-2.06-0.1.fc32.x86_64.rpm | ||
| qubes-src/grub2/pkgs/dom0-fc32/x86_64/grub2-tools-minimal-debuginfo-2.06-0.1.fc32.x86_64.rpm | ||
| ``` |
There was a problem hiding this comment.
And what when I will have packages? What I can do with those? How to use them?
| our fork). To fetch manually run following command. | ||
|
|
||
| ```bash | ||
| $ FETCH_CMD="curl --proto '=https' --proto-redir '=https' --tlsv1.2 --http1.1 -sSfL -o" make get-sources |
There was a problem hiding this comment.
You can call make get-sources-extra COMPONENTS="vmm-xen grub2" from qubes-builder dir, to avoid specifying this manually.
|
Cleanup: do we want to proceed with this PR? |
…es packages
Signed-off-by: Michał Żygowski [email protected]
Signed-off-by: Tomasz Żyjewski [email protected]