[FEAT] ci/cd binary package artifacts should be build and published

[sassman]

When building a new tag, binary packages should be generated and attached to the github releases page.

[sassman]

This depends on #11 and must be tackled after.

[tunnckoCore]

Waiting. :)

Seems like a cool project and definitely more maintained than the steghide which is since 2003.

I'm trying to get it on openSUSE Thumbleweed. For some reason compiling it with rust fails (with linker 'cc' not found and could not compile rayon-core), but it can be due to my read-only filesystem. Anyway, i'm reinstalling it soon so we we'll see.

[sassman]

Hey @tunnckoCore ,

Thanks for the feedback. I believe one of the dependencies needs gcc in order to compile.

Try to install gcc and then retry. If it woks I have to update the docs to make that more obvious.

[sassman]

PS: there is a snap that you can also install and use on open suse (see the readme). As an alternative to building from source.

[tunnckoCore]

Ah thanks, I'll try.

I've seen the support of snap, the thing is i like to stick to the OS original package manager (on any os).

[tunnckoCore]

Yep. Seems to like that approach, installed gcc. Compiled.

[sassman]

I've seen the support of snap, the thing is i like to stick to the OS original package manager (on any os).

So would you only consider RPMs or would you be open to an AppImage binary as well? I'm asking because somebody suggested AppImage on #15

So would be happy to get more feedback in this regard.

[tunnckoCore]

Don't use AppImages and don't like the idea very much. I'm for all kind of binaries and packages. A deb, rpm and aur is enough.