How I can do it? For example I want to build mpd with full multimedia codec support (because the Packman team ignores everything requests update their out of date build). I don’t plan to publish this build, I want to build it for myself.
So, how I can add missing packages to successfully build mpd? Should I build they into my repo too or I can add link to existing ones?
You could request an account at the Packman build service, they use OBS as well, linked to the main instance.
You could then even update mpd on Packman yourself… 
So, how I can add missing packages to successfully build mpd? Should I build they into my repo too or I can add link to existing ones?
ffmpeg and friends are prohibited on OBS.
But there’s the repo home:RedDwarf:fakePackman, that contains devel packages for most of the multimedia packages from Packman stripped off of real code (and therefore “legal”).
Either branch the packages you need from there in your repo, or add that to the repos yours builds against.
http://software.opensuse.org/package/ffmpeg
Is it temporary or “prohibited” only by words? 
I read Build Service Tutorial from openSUSE site and found, that I can build package locally into chroot by using OSC.
“osc will connect to the OBS repository server and download all needed RPMs to /var/tmp/osbuild-packagecache/plattform/repository/arch as cache directory”
So, if I manually add to this path packages from packman, will it build mpd successfully?
As I understand, it doesn’t bloats my system?
Hi
I’ve branched the package on packman and will look at updating to 0.19.3…will see how it goes.
Those are private home: repos. Apparently nobody noticed yet that they build something illegal, but that might change at any point and those packages might disappear.
See here:
https://en.opensuse.org/openSUSE:Build_Service_application_blacklist
So, if I manually add to this path packages from packman, will it build mpd successfully?
I don’t think so. This is only a cache for downloaded packages. You would have to install them in the build chroot.
Probably mpd will see them/take them from there if you specify them as BuildRequires, I don’t know.
As I understand, it doesn’t bloats my system?
What do you mean with that.
Still, I would just build against RedDwarf’s fakePackman packages (I do, in fact).
And I don’t understand why you complain that Packman doesn’t update it and want to build it yourself, but won’t offer to update yourself/build it on Packman for everybody… :
Help is always welcome there.
Tutorial tells: “If you want to avoid network traffic, its possible to fill the cache beforehand with rpms from a DVD or iso. For that, copy the rpms from the DVD to the cache dir”. So I believe it should work. I hope…
I mean that this install into chroot, and all of -devel packages doesn’t bloats my system?
I’ll try it, thanks.
I’m newbie in packaging. And just started trying to do it. So I think a lot of users will say me “Thanks” if I will not touch packman’s mpd
Hi
So at this point it needs automake 1.14, which is in factory at the moment, not 13.2. plus it’s errors out on the build with undefined reference errors, trying a factory build first…
Hi
See http://lists.links2linux.de/pipermail/packman/2014-November/013305.html it’s updated, but have an issue…