English Finnish
Additional annotated templates Muita selitettyjä malleja
Additional resources
Advanced uses cases Edistyneet käyttötapaukset
A Go package is identified by its import path. A Go spec file will therefore start with the `+%{goipath}+` declaration. Don't get it wrong, it will control the behaviour of the rest of the spec file.
All macros, including package name, source URL, will be computed from this value. Kaikki makrot, mukaan lukien paketin nimi ja lähde-URL, johdetaan tästä arvosta.
And, finally, if you wish to split the project Go code in multiple packages, you can compute the corresponding names with: Ja lopuksi, jos haluat jakaa projektin Go-koodin useisiin paketteihin, voit muodostaa vastaavat nimet seuraavasti:
And the possible documentation that SHOULD be included:
an rpm-compatible package name derived from goipath
archiveext
archivename
archiveurl
# A space-separated list of import paths to simulate.
%global goaltipaths
# Välilyönnillä eroteltu luettelo simuloitavista tuontipoluista.
%global goaltipaths
As said before, you MUST run unit tests in `+%check+`:
At the moment golang projects packaged in Fedora SHOULD be unbundled by default. It means projects are built from dependencies packaged in Fedora.
a URL that can be used as SourceX: value
a URL that can be used as URL: value
Automatic BuildRequires
Automatic Dependency Generation
Be wary of command names which might already exist in Fedora. If you have any doubt, you can check if the command is already provided in Fedora:
Binaries are usually shipped in the main package. This package MUST include legal files and documentation associated with those binaries.