778
edits
Changes
Jump to navigation
Jump to search
Line 51:
Line 51: − + Line 71:
Line 71: − + − + − + Line 80:
Line 80: − +
Howto interact with gitea and koji to do an rpm build for SME11 (view source)
Revision as of 08:52, 28 August 2024
, 28 August→Gitea
The Gitea server is available [https://src.koozali.org here].If you are serious about developing systems for SMEServer, then you will need a user. There is a central authorization system, and you can be entered into it by a request to [mailto:contact@koozali.org contact@koozali.org]
The Gitea server is available [https://src.koozali.org here].If you are serious about developing systems for SMEServer, then you will need a user. There is a central authorization system, and you can be entered into it by a request to [mailto:contact@koozali.org contact@koozali.org]
There are two relevant ''organisations'' on the gitea server ''smeserver'' and ''smecontribs.'' One for the core components and one for the contribs.
There are two relevant ''organisations'' on the gitea server ''smeserver'' and ''smecontribs.'' One for the core components and one for the contribs. These are just a useful way or categorizing and grouping repositories.
The common directories are necessary if you are to do either local rpm builds or insert build requests into koji. The common directory contains the necessary makefile code.
The common directories are necessary if you are to do either local rpm builds or insert build requests into koji. The common directory contains the necessary makefile code.
</syntaxhighlight>
</syntaxhighlight>
To bring down a specific package, these are the commands are:<syntaxhighlight lang="shell">
To bring down a specific package, the commands are:<syntaxhighlight lang="shell">
cd smeserver #or smecontribs
cd smeserver #or smecontribs note this is the directory above the package directory
git clone https://src.koozai.org/<packagename>.git
git clone https://src.koozali.org/<organisation>/<packagename>.git
</syntaxhighlight>
</syntaxhighlight>
Note that git clone will not overwrite a previous directory containing an earlier (or the same) version of the package. This is so that you do not inadvertently overwrite precious changes you might have made.
Note that git clone will not overwrite a previous directory containing an earlier (or the same) version of the package. This is so that you do not inadvertently overwrite precious changes you might have made.
To check that all changes have been written to git, run git status in the directory and it will show you (in red) all files which are different from the ones on the gitea server.
To check that all changes have been written to git, run ''git status'' in the directory and it will show you (in red) all files which are different from the ones on the gitea server.
=Koji=
=Koji=