Hello, On Tue, 09 Aug 2011, Adrian Schröter wrote:

Am Dienstag, 9. August 2011, 18:15:57 schrieb David Haller:

...

please remind me, what's the way to build against packman stuff like ffmpeg (i.e. libav* etc.)?

go to packman, they have an OBS too ;)

I've been unsuccessfully looking for it ... Seems, I'll need a packman account first [1].

...

If there isn't already, there are so many cross-dependancies, I think there should be at least a "use-for-build"-only repo in the OBS (or as a link to the PM OBS?), which probably would need some coordination with the packman guys, but as some personnel is shared ...

You can build against build.o.o in packman OBS. We can't host the binaries, also not for compile-time-only, because it must be possible to download them for a local build.

Plausible. Sucks though not being able to build in your home:<nick> against e.g. (packman) ffmpeg. It _is_ frustrating, though understandable. I wish some "linking" were possible (i.e. DL directly from packman (OBS) for local builds, and DL (from Packman (OBS)) as not-published-use-for-build-only when building in obs://build.opensuse.org/home:*). Sample: I've locally packaged with "osc build" (with some tricks and locally copied libav*.so.* from /usr to /var/tmp/build/...) http://code.google.com/p/vstripe that links against libav* amongst others. That code itself is (AFAIK) unencumbered, so hosting the binary should pose no problem. It _links_ to ffmpeg's libav* though. Being unable to package stuff like that in the OBS is frustrating, see the many many "FakePackman" (etc.) packages in the obs. I think "we" or OBS need some solution for this. Let the landsharks earn their pay, let them figure out a way out of our dilemma of how to build/link against packman packages without resorting to a) actually add the package to one's repo or b) creating a "Fake" RPM or c) well, build at packman. -dnh, it's not that I can't build stuff locally[0] [0] I used to run a former SuSE 6.2 with partly up-to-date software up until last year on my old box, and only some updates were as RPMs. I have a low threshold about "hacking" stuff (esp. build-stuff, less so actual code) to work ;) Build-stuff like a "configure" I like to "patch" via an sed/perl -i in the %prep section. Usually easier than patching configure.{in,ac} and regenerating configure. Work{ed,s} for me. Now, using 11.x, I try to do clean patches and build in OBS if I have the nerve. [1] if anyone from packman reads this, please read this as an application. --

...

there is nothing new under the Sun. Having seen the stuff growing in the spilt coffee under the Sun of an ex-cow-orker I'm not sure that's true! Does it greet you when you come in in the morning? [Rik Steenwinkel] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 2011-08-09 22:35:19 (+0200), David Haller wrote:

On Tue, 09 Aug 2011, Adrian Schröter wrote:

...

Am Dienstag, 9. August 2011, 18:15:57 schrieb David Haller:

...

please remind me, what's the way to build against packman stuff like ffmpeg (i.e. libav* etc.)?

go to packman, they have an OBS too ;)

I've been unsuccessfully looking for it ... Seems, I'll need a packman account first [1].

Yes. True, there isn't all that much google-able information about how to do that. But we (packman) have a mailing-list that isn't too difficult to find, as well as an IRC channel (#packman on freenode).

...

...

If there isn't already, there are so many cross-dependancies, I think there should be at least a "use-for-build"-only repo in the OBS (or as a link to the PM OBS?), which probably would need some coordination with the packman guys, but as some personnel is shared ...

You can build against build.o.o in packman OBS. We can't host the binaries, also not for compile-time-only, because it must be possible to download them for a local build.

Plausible. Sucks though not being able to build in your home:<nick> against e.g. (packman) ffmpeg.

It _is_ frustrating, though understandable.

But as Adrian wrote above, you can poke us for an account on the Packman OBS instance (we refer to it as "PMBS" (PackMan Build Service ;)). And you can link anything that is on build.o.o into Packman -- we actually do that a lot, to avoid duplication of efforts. Quite a few packages are maintained in build.o.o and have a special %if in it to enable support for stuff you only find in Packman (e.g. ffmpeg). We just link to that in PMBS and given that those special %if's are enabled in PMBS, it builds the same version but with full codec support in the Packman repository.

I wish some "linking" were possible (i.e. DL directly from packman (OBS) for local builds, and DL (from Packman (OBS)) as not-published-use-for-build-only when building in obs://build.opensuse.org/home:*).

Just do it the other way around, build against things that are on build.o.o with PMBS. On a side note, we do have a few build hosts and you don't need to wait any longer for builds to finish than on build.o.o (typically the opposite, actually). So there's no drawback in building against PMBS instead of against build.o.o (directly).

Sample: I've locally packaged with "osc build" (with some tricks and locally copied libav*.so.* from /usr to /var/tmp/build/...) http://code.google.com/p/vstripe that links against libav* amongst others. That code itself is (AFAIK) unencumbered, so hosting the binary should pose no problem. It _links_ to ffmpeg's libav* though.

Being unable to package stuff like that in the OBS is frustrating, see the many many "FakePackman" (etc.) packages in the obs.

Yeah well it's still the wrong way around. The much, much simpler option is the most straightforward one: poke us at packman to get an account on PMBS. [...]

[1] if anyone from packman reads this, please read this as an application.

Too many lists to follow :) For future reference: please poke us at packman@links2linux.de (no need to subscribe, though it's a requirement once you have an account and publish packages, for obvious reasons) or on irc://irc.freenode.net/packman (poke yaloki or detlef). cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf

* David Haller (dnh@opensuse.org) [20110815 09:12]:

As I've done last Thursday ;) I'm still somewhat wrestling with osc though, i.e. when do I need to use '-A' (which I've aliased). Luckily not with 'osc build', so I can keep using my wrappers unmodified ;)

You always need to use -A for packman. The alias only allows you to use '-A <alias>' instead of '-A <apiurl>'. I use bash aliases or functions like to ease it for me. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

* Adrian Schröter (adrian@suse.de) [20110815 14:12]:

It should not be needed when you are in a checked out project or package directory.

That's true. But the annoying thing is that you can't override what's stated in the files below .osc. So while in a packman project/package you can't even query a different build service because -A is ignored when that info is present. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org