Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-05-02 14:56:13 -04:00
Code Issues Projects Releases Packages Wiki Activity

Resolve open issues mentioned on Transifex

Browse source
This commit is contained in:
Tobias Killer 2021-04-17 10:31:11 +02:00
parent 617330d026
commit 190b740e32
No known key found for this signature in database
GPG key ID: 2DA5EF6F6E40B328
4 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

8
developer/building/development-workflow.md
View file

@ -117,7 +117,7 @@ cd ../..
vi series.conf
~~~
#### Building RPMS
#### Building RPMs
TODO: Is this step generic for all subsystems?
@ -130,13 +130,13 @@ distinguish between different versions of the same package.
You might want to take a moment here to review (git diff, git status), commit
your changes locally.
To actually build RPMS, in qubes-builder:
To actually build RPMs, in qubes-builder:
~~~
make linux-kernel
~~~
RPMS will appear in qubes-src/linux-kernel/pkgs/fc20/x86\_64:
RPMs will appear in qubes-src/linux-kernel/pkgs/fc20/x86\_64:
~~~
-rw-rw-r-- 1 user user 42996126 Nov 17 04:08 kernel-3.4.18-1debug20121116c.pvops.qubes.x86_64.rpm
@ -166,7 +166,7 @@ FETCH_HEAD` (in each repo directory). Or `make do-merge` to merge all of them.
When developing it is convenient to be able to rapidly test changes. Assuming
you're developing Qubes on Qubes, you should be working in a special VM for
Qubes and occasionally you will want to transfer code or rpms back to dom0 for
Qubes and occasionally you will want to transfer code or RPMs back to dom0 for
testing.
Here are some handy scripts Marek has shared to facilitate this.

2
developer/building/qubes-builder.md
View file

@ -99,7 +99,7 @@ cp example-configs/qubes-os-master.conf builder.conf
make get-sources
# And now to build all Qubes rpms (this will take a few hours):
# And now to build all Qubes RPMs (this will take a few hours):
make qubes