KiwiBirdsDev
Posts: 1
Joined: Sun Nov 25, 2018 5:33 am

Making a eopkg package from a C program

Sun Nov 25, 2018 5:42 am

EDIT: I GOT IT WORKING AFTER WORKING ON IT FOR 4 1/2 hours

Hello, I'm trying to make a eopkg package for my C program, which is a text editor.

Link: https://github.com/Bird-dev/test/tree/m ... %20v0.0.1a

This is my packages.yml file:

Code: Select all

name       : eagle
version    : 0.0.1a
release    : 1
source     : https://github.com/Bird-dev/test/blob/master/Eagle%20v0.0.1a/Debian/eagle.deb : 9bd1fa4f4cdcf986cc45e36b37b1bac0a4234782
license    : MIT
summary    : Small command line editor
component  : system.devel
description: A nice and easy to use text editor in my suite of Applications for my Operating System Bird OS.
And this is my output when I try to run "sudo solbuild build"

Code: Select all

kiwi@solus ~/test/eagle $ sudo solbuild build
Failed to load package: yaml: line 3: mapping values are not allowed in this context
kiwi@solus ~/test/eagle $ 
And if I try to use make it has more of an output:

Code: Select all

kiwi@solus ~/test/eagle $ make
make build
make[1]: Entering directory '/home/kiwi/test/eagle'
sudo solbuild build package.yml -p unstable-x86_64; 
Password: 
Failed to load package: yaml: line 3: mapping values are not allowed in this context
make[1]: Leaving directory '/home/kiwi/test/eagle'
make abireport
make[1]: Entering directory '/home/kiwi/test/eagle'
abireport -p abi_ -D `dirname package.yml` scan-packages `dirname package.yml`
Error locating packages: No packages in directory .

make[1]: *** [../Makefile.common:15: abireport] Error 1
make[1]: Leaving directory '/home/kiwi/test/eagle'
make: *** [../Makefile.common:12: complete] Error 2
kiwi@solus ~/test/eagle $ 
What am I doing wrong? Is it not possible to make C programs into .eopkg packages? Thank you all for helping :)

User avatar
kyrios
Posts: 2349
Joined: Thu Sep 22, 2016 4:20 pm

Re: Making a eopkg package from a C program

Sun Nov 25, 2018 11:41 am

Why do you package it in .deb then unpack it to repack it in eopkg format ?
Why not just making a release of the source code in github and start from there ?

Also 2nd half of the info are here because why posting all the info at the same place... ;)

Return to “Engagement”