Include:Abuild-configure: Difference between revisions
Prabuanand (talk | contribs) (created new Include page) |
Prabuanand (talk | contribs) (Modified the content so that only configuration information also remains) |
||
| Line 1: | Line 1: | ||
Abuild needs to be configured for both the system and user. | |||
Edit the file {{Path|/etc/abuild.conf}} as per requirements. Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create. | Edit the file {{Path|/etc/abuild.conf}} as per requirements. Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create. | ||
Revision as of 08:45, 18 February 2025
Abuild needs to be configured for both the system and user.
Edit the file /etc/abuild.conf as per requirements. Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.
In order to use abuild command The user executing abuild must be a member of the abuild group:
# addgroup <yourusername> abuild
Note: Remember to logout and login again for the group change to have effect.
For abuild a public/private rsa key pair is needed. The abuild-keygen command from abuild package generates and configures the security keys.
$ abuild-keygen -a -i