778
edits
Changes
Jump to navigation
Jump to search
Line 88:
Line 88: − + + + + + + +
Howto interact with gitea and koji to do an rpm build for SME11 (view source)
Revision as of 14:17, 28 August 2024
, 28 August→Editing the Source Code
= Editing the Source Code=
= Editing the Source Code=
As described above you can pull down the repo for a specific package using the git clone command. Or you can use the gitea web interface to grab which ever file you want and edit it as required, even using the provided gitea editor. You may be able to configure your desktop editor to interact with the remote gitea/git.
As described above you can pull down the repo for a specific package using the git clone command. Or you can use the gitea web interface to grab which ever file you want and edit it as required, even using the provided gitea editor. You may be able to configure your desktop editor to interact with the remote gitea/git. You can then commit the changes using your editor or the gitea editor/web pages.
My preferred modus operandi is to use a running (and fully updated) SME11 VM to which I have full file access from my desktop using the sshfs package. This allows me to make any changes using my preferred source code editor (geany in my case) and fully test any changes in place, and then copy the changed files back to the build system ready for local rpm build and test before updating to gitea/git and then doing a koji build. YMMV.
My preferred modus operandi is to use a running (and fully updated) SME11 VM to which I have full file access from my desktop using the sshfs package. This allows me to make any changes using my preferred source code editor (geany in my case) and fully test any changes in place, and then copy the changed files back to the build system ready for local rpm build and test before updating to gitea/git and then doing a koji build. YMMV.
=Local rpm build=
=Local rpm build=
A local rpm build can be achieved using ''mock''. You can do it by issuing the following command:
make mockbuild
While positioned in the cloned directory. mock will read the data in the directory (NOT from git) and create a src and binary rpm. This can then be copied to the test VM and tried.
=Saving the Source code to Gitea=
=Saving the Source code to Gitea=
All these commands take place while positioned in the cloned directory for the package.
All these commands take place while positioned in the cloned directory for the package.