On Mon, 2026-08-31 at 20:00 +0200, Manfred Hollstein wrote:
> Hi there,
>
> the more I think about Packman potentially going away, the more I ask
> myself, what is it really that Packman has over those packages coming
> from OBS. I know this BUILD_ORIG and BUILD_ORIG_ADDON thing defined
> in
> Essentials' project config which can be/is used in packages with
> patent
> encumbered content like ffmpeg and others. Does anyone *know* what we
> would be missing if we would be using just those packages from OBS
> instead of the version from Packman? I know of one package, at least,
> which wouldn't be possible to be provided within OBS, which is
> libdvdcss. Even on Packman there are no sources for the package, just
> the .spec file, but that's not a problem for people who can read a
> .spec
> file. The same is probably true for the whole Bluray stuff.
BUILD_ORIG usually restores access to codecs SUSE/openSUSE can not ship
on OBS. for many free-ish codecs this isnt needed but e.g. for others
like hevc or codec access in Mesa.
but packman isnt just those codec packages.
could the list maybe reviewed and shortened? sure. like probably many
other projects on the OBS it might also be worth checking if all
packages are still maintained.
> FWIW, I think I'll try to build kodi/kodi.binary-addons on OBS and
> see
> how that works in my environment. The same is true for handbrake and
> MakeMKV. Will keep you posted.
> FWIW2, broadcom-wl is available on OBS and not necessarily bound to
> Packman at all.
Keep in mind that codecs arent the only things that can not go onto
OBS.
darix
--
Always remember:
Never accept the world as it appears to be.
Dare to see it for what it could be.
The world can always use more heroes.
_______________________________________________
Packman mailing list
[email protected]
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
