On 21. 11. 24 23:11, William Cohen wrote:
Sediment has been designed to work with the RPM build process.
Currently, one needs to use modified RPM macros. These can be created
quickly by writing the output of the sediment make_sediment_rpmmacros
command into ~/.rpmmacros. One will also need to define set the pgo
macro to 1 for the rpmbuild process. The rpm spec file has minimal
modifications. It has the callgraph files stored as a source file and
a defines the global call_graph to the source file that holds the call
graph.
Hey Will,
let's say I wan to try this for Python. Where do I start? The README on
https://github.com/wcohen/sediment is not very helpful.
This is what I did based on your email:
$ sudo dnf --enable-repo=updates-testing install sediment
...
Installing sediment-0:0.9.3-1.fc41.noarch
I run make_sediment_rpmmacros, it gives me some macros. Now I am supposed to
put those to ~/.rpmmacros. Exccept I never build Python loclly, I use Koji or
mock. I can probably amend this to use %global and insert it to
python3.14.spec. But what else I need to do? Do you have a step by step kind of
document I can follow?
--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
