Bug 28518

Fedora has this package already.

Source RPM: libseccomp => https://download-ib01.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/source/tree/Packages/l/libseccomp-2.5.0-4.fc34.src.rpm

we dont add static libs unnecessarily, especially for something we dont support.

No harm meant by asking, but why then do we offer so many other static packages?

urpmq -y static

boinc-client-static
busybox-static
cddlib-static
dash-static
glibc-static-devel
hdf-static
java-11-openjdk-static-libs
llvm-static
llvm10-static
mingw32-SDL2-static
mingw32-angleproject-static
mingw32-antlr-static
mingw32-atk-static
mingw32-boost-static
mingw32-bzip2-static
mingw32-cairo-static
mingw32-cairomm-static
mingw32-celt051-static
mingw32-curl-static
mingw32-dbus-glib-static
mingw32-dbus-static
mingw32-dlfcn-static
mingw32-enchant-static
mingw32-expat-static
mingw32-fftw-static
mingw32-fontconfig-static
mingw32-freetype-static
mingw32-fribidi-static
mingw32-gdbm-static
mingw32-gettext-static
mingw32-giflib-static
mingw32-glew-static
mingw32-glib2-static
mingw32-glibmm24-static
mingw32-gsl-static
mingw32-gtk2-static
mingw32-gtkglext-static
mingw32-gtkhtml3-static
mingw32-gtkspell3-static
mingw32-gtkspellmm30-static
mingw32-harfbuzz-static
mingw32-hunspell-static
mingw32-jasper-static
mingw32-lcms-static
mingw32-lcms2-static
mingw32-leptonica-static
mingw32-libarchive-static
mingw32-libffi-static
mingw32-libgcrypt-static
mingw32-libgeotiff-static
mingw32-libglade2-static
mingw32-libgnurx-static
mingw32-libgpg-error-static
mingw32-libgsf-static
mingw32-libidn-static
mingw32-libidn2-static
mingw32-libjpeg-turbo-static
mingw32-libpng-static
mingw32-libsigc++20-static
mingw32-libssh2-static
mingw32-libtiff-static
mingw32-libvirt-static
mingw32-libxml2-static
mingw32-libxslt-static
mingw32-openjpeg-static
mingw32-openssl-static
mingw32-pango-static
mingw32-pcre-static
mingw32-pixman-static
mingw32-portablexdr-static
mingw32-readline-static
mingw32-sqlite-static
mingw32-termcap-static
mingw32-win-iconv-static
mingw32-winpthreads-static
mingw32-xz-libs-static
mingw32-zlib-static
mingw64-SDL2-static
mingw64-angleproject-static
mingw64-antlr-static
mingw64-atk-static
mingw64-boost-static
mingw64-bzip2-static
mingw64-cairo-static
mingw64-cairomm-static
mingw64-celt051-static
mingw64-curl-static
mingw64-dbus-glib-static
mingw64-dbus-static
mingw64-dlfcn-static
mingw64-enchant-static
mingw64-expat-static
mingw64-fftw-static
mingw64-fontconfig-static
mingw64-freetype-static
mingw64-fribidi-static
mingw64-gdbm-static
mingw64-gettext-static
mingw64-giflib-static
mingw64-glew-static
mingw64-glib2-static
mingw64-glibmm24-static
mingw64-gsl-static
mingw64-gtk2-static
mingw64-gtkglext-static
mingw64-gtkhtml3-static
mingw64-gtkspell3-static
mingw64-gtkspellmm30-static
mingw64-harfbuzz-static
mingw64-hunspell-static
mingw64-jasper-static
mingw64-lcms-static
mingw64-lcms2-static
mingw64-leptonica-static
mingw64-libarchive-static
mingw64-libffi-static
mingw64-libgcrypt-static
mingw64-libgeotiff-static
mingw64-libglade2-static
mingw64-libgnurx-static
mingw64-libgpg-error-static
mingw64-libgsf-static
mingw64-libidn-static
mingw64-libidn2-static
mingw64-libjpeg-turbo-static
mingw64-libpng-static
mingw64-libsigc++20-static
mingw64-libssh2-static
mingw64-libtiff-static
mingw64-libvirt-static
mingw64-libxml2-static
mingw64-libxslt-static
mingw64-openjpeg-static
mingw64-openssl-static
mingw64-pango-static
mingw64-pcre-static
mingw64-pixman-static
mingw64-portablexdr-static
mingw64-readline-static
mingw64-sqlite-static
mingw64-termcap-static
mingw64-win-iconv-static
mingw64-winpthreads-static
mingw64-xz-libs-static
mingw64-zlib-static
popt-static
python3-django-staticinline
python3-flask-multistatic
qemu-user-static
rust-std-static

Don't get me wrong, I could build it locally myself, but I'd rather have it added to the repos so that it would be easier to just do urpmi snapd.spec --auto in the future.

The whole thing about adaptation is the key to make things work.
Maybe we could have a poll on the front page of mageia.org to see if people would like to have snapd in the near future?

(In reply to Thomas Backlund from comment #2)
> we dont add static libs unnecessarily, especially for something we dont
> support.
The last phrase seems rather important.
Is this not really a request for 'snapd' itself: yet another self-contained application repository, like Flatpack and AppImage? If so, what is the advantage of snapd over these?

> Fedora has this package already. [libseccomp-static]
Cannot you use that directly? Sometimes RPMs from other distributions work.

And there is always the question of: become a packager and maintain the SRPMs you want. You clearly have the knowhow.

CC: (none) => lewyssmith

https://download-ib01.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/source/tree/Packages/l/libseccomp-2.5.0-4.fc34.src.rpm

Assigning this package request to all packagers collectively. On a voluntary basis, one of them might, if there are no license or other legal issues, want to integrate it to the distribution and maintain it for bug and security fixes.

You Kristoffer might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Source RPM: https://download-ib01.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/source/tree/Packages/l/libseccomp-2.5.0-4.fc34.src.rpm => (none)
Assignee: bugsquad => pkg-bugs
Version: 8 => Cauldron
Severity: normal => enhancement

I took the liberty of packaging libseccomp for Mageia 8 by adapting the spec file from Fedora:

https://drive.google.com/file/d/17g99751bn4fv4VhkQA3NX5EH6urP68TM/view?usp=sharing

This will also build libseccomp-static.

Note: I couldn't find another file storage site at first thought, that's why I put it in my drive.

Nope, 
we are moving towards less static packages, not more...

just because fedora provides a package does not mean we have to...

and we dont need another useless unmaintained package

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED

(In reply to Thomas Backlund from comment #7)
> Nope, 
> we are moving towards less static packages, not more...
> 
> just because fedora provides a package does not mean we have to...
> 
> and we dont need another useless unmaintained package

No offence meant, but if we say that one wants to build........ Telegram directly from source and the spec file tells you to use libseccomp-static since libseccomp won't work to build it, how do I lower the number of steps to actually build it from source?

I'm just saying.

Again...... No harm meant.

I just view it differently.

File a bug with the telegram developers.