| *** franred [~franred@82-68-191-81.dsl.posilan.com] has joined #baserock | 07:48 | |
| *** tiagogomes [~tiagogome@access.ducie-dc1.codethink.co.uk] has joined #baserock | 08:05 | |
| *** jonathanmaw [~jonathanm@82-68-191-81.dsl.posilan.com] has joined #baserock | 08:29 | |
| *** ssam2 [~ssam2@82-68-191-81.dsl.posilan.com] has joined #baserock | 09:16 | |
| *** locallycompact [~lc@82-68-191-81.dsl.posilan.com] has joined #baserock | 09:20 | |
| *** stetaylor [~stetaylor@82-68-191-81.dsl.posilan.com] has joined #baserock | 09:23 | |
| *** locallycompact [~lc@82-68-191-81.dsl.posilan.com] has quit [Remote host closed the connection] | 11:03 | |
| *** locallycompact [~lc@82-68-191-81.dsl.posilan.com] has joined #baserock | 11:05 | |
| *** tiagogomes [~tiagogome@access.ducie-dc1.codethink.co.uk] has quit [Ping timeout: 244 seconds] | 11:14 | |
| *** tiagogomes [~tiagogome@access.ducie-dc1.codethink.co.uk] has joined #baserock | 11:18 | |
| *** stetaylor [~stetaylor@82-68-191-81.dsl.posilan.com] has quit [Remote host closed the connection] | 11:30 | |
| ssam2 | doh, gstreamer in baserock doesn't build because of -Werror | 11:39 |
|---|---|---|
| ssam2 | seems nothing has changed in the gstreamer baserock/genivi/baseline branch since 2012, though | 11:42 |
| ssam2 | as far as I know neither have we changed eglibc or GCC | 11:42 |
| ssam2 | hmm, we have updated GLib, though | 11:45 |
| rjek | Glib and Gtk are famous for breaking things that used to work due to a never-ending cycle of deprecation. | 11:45 |
| radiofree | are you talking about gstreamer 0.10 ssam2 | 11:45 |
| radiofree | i sent patches for that on the 23/06/14 "[PATCH 0/7] Fix gstreamer 0.10 build with newer glibs" | 11:46 |
| *** stetaylor [~stetaylor@94.118.167.181] has joined #baserock | 11:47 | |
| ssam2 | I thought gstreamer 1, but now I'm not so sure | 11:49 |
| ssam2 | no, definitely gstreamer1 | 11:49 |
| ssam2 | I'm trying to build the GENIVI baseline | 11:49 |
| radiofree | ah | 11:49 |
| ssam2 | I'd like to fix this by just updating to GStreamer 1.4 | 11:50 |
| ssam2 | but I don't want to spend time fixing any new issues that might introduce, this was already a tangent | 11:50 |
| radiofree | ssam2: see [PATCH 3/7] Automatic update of common submodule | 11:50 |
| radiofree | submodule is probably pointing at an old sha in gstreamer-common | 11:51 |
| ssam2 | seems so | 11:51 |
| ssam2 | thanks for pointing that out | 11:51 |
| ssam2 | i'm not quite sure where it *should* be pointing to, though, how do I find that out? | 11:52 |
| ssam2 | presumably for 0.10 and 1.2 the answer to that question is different | 11:52 |
| * paulsherwood thought jjardon had done this already | 11:53 | |
| radiofree | yeah, HEAD for 1.2 branch? | 11:53 |
| radiofree | also what paulsherwood said.. | 11:53 |
| ssam2 | oh, you're right. I missed that | 11:54 |
| paulsherwood | has jjardon's stuff been reviewed? merged? | 11:56 |
| ssam2 | no, it's still outstanding | 11:58 |
| ssam2 | at least, the gstreamer fixes are outstanding | 11:58 |
| ssam2 | I merged the gtk patch series he sent | 11:58 |
| ssam2 | I'd like to review his gstreamer stuff, but i'm in the middle of doing something else | 11:58 |
| straycat | http://sprunge.us/SVBF is a quick patch to change where we get git-fat from. | 12:07 |
| *** doffm [~mdoff@23.226.235.108] has joined #baserock | 12:12 | |
| *** tiagogomes_ [~tiagogome@access.ducie-dc1.codethink.co.uk] has joined #baserock | 12:12 | |
| ssam2 | straycat: thanks. Why is this patch needed? | 12:14 |
| straycat | I don't know in detail, other than that it's better and it's the repo that gets linked from python.org | 12:15 |
| ssam2 | straycat: ok. well +1 from me, hopefully someone who knows more about git-fat than I do can comment though | 12:19 |
| Kinnison | Well, it's a potentially newer git-fat but without reviewing what has changed I can't say how it will affect morph etc | 12:20 |
| Kinnison | so I'd be +0.5 on the lorry change but would -10 any attempt to use it yet | 12:20 |
| straycat | *nod* | 12:21 |
| straycat | It should probably be tested before merging. | 12:21 |
| Kinnison | What prompted you to want to provide the patch? | 12:21 |
| straycat | We couldn't build some software because our trove lorried this git-fat from gbo rather than the "official" one. | 12:22 |
| richard_maw | the situation is a bit odd, since the cyaninc one is a fork of the one we're currently using | 12:23 |
| richard_maw | but the cyaninc one has tags and is the one pip uses | 12:23 |
| Kinnison | So the cyaninc one is a fork of jedbrown's but jedbrown's still is under development | 12:25 |
| Kinnison | and cyaninc aren't merging his work | 12:25 |
| Kinnison | I'd be more tempted to move to the tip of jedbrown's work than to switch to a different provider unless cyaninc's is definitively better in some manner | 12:26 |
| Kinnison | (note, "this is the one pip uses" is actually a negative strike for me because I find pip to generally be awful) | 12:26 |
| * straycat nods | 12:28 | |
| *** stetaylor [~stetaylor@94.118.167.181] has quit [Remote host closed the connection] | 12:36 | |
| *** stetaylor [~stetaylor@82-68-191-81.dsl.posilan.com] has joined #baserock | 12:57 | |
| jjardon | rjek: nothing should break because you deprecate things | 13:05 |
| jjardon | deprecate means its deprecated, not removed | 13:06 |
| rjek | jjardon: Unless people use -Werror | 13:12 |
| jjardon | then is a problem of the people that use -Werror, not the library that deprecate API | 13:13 |
| rjek | No, -Werror is very useful. It means that code that may be depending on undocumented, unspecified, or changed functionality won't build until somebody decides that the resulting binary won't destroy all your data. | 13:14 |
| rjek | I never want to trust my important data to an application that the compiler wasn't sure about how to compile, and emitted a warning that got lost in thousands of lines of build output, tbh. | 13:15 |
| jjardon | Werror means the compilation fails if there is a compilation error. In this case it fails because you are used perfectly documented and correct API, but deprecated: its is ok if the compilation fails, as thats your choice when you choose to use -Werror, but not the fault of the library that decide to deprecate some api | 13:30 |
| *** stetaylor [~stetaylor@82-68-191-81.dsl.posilan.com] has quit [Remote host closed the connection] | 13:35 | |
| *** stetaylor [~stetaylor@217.137.226.146] has joined #baserock | 14:02 | |
| *** stetaylor [~stetaylor@217.137.226.146] has quit [Remote host closed the connection] | 14:33 | |
| *** tiagogomes_ [~tiagogome@access.ducie-dc1.codethink.co.uk] has quit [Ping timeout: 264 seconds] | 15:52 | |
| *** jonathanmaw [~jonathanm@82-68-191-81.dsl.posilan.com] has quit [Quit: Leaving] | 16:30 | |
| ssam2 | I've just thought of one negative side-effect of chunks-in-definitions | 16:52 |
| ssam2 | creating a temporary build branch is already slow, and this will make it WAY slower still | 16:52 |
| ssam2 | I think | 16:52 |
| *** franred [~franred@82-68-191-81.dsl.posilan.com] has quit [Quit: Leaving] | 16:54 | |
| *** sambishop [~sambishop@82-68-191-81.dsl.posilan.com] has quit [Ping timeout: 264 seconds] | 17:14 | |
| *** locallycompact [~lc@82-68-191-81.dsl.posilan.com] has quit [Ping timeout: 250 seconds] | 17:33 | |
| *** sambishop [~sambishop@95.144.14.182] has joined #baserock | 17:44 | |
| *** ssam2 [~ssam2@82-68-191-81.dsl.posilan.com] has quit [Remote host closed the connection] | 17:46 | |
| *** stetaylor [~stetaylor@2.223.131.74] has joined #baserock | 17:54 | |
| *** stetaylor [~stetaylor@2.223.131.74] has quit [Remote host closed the connection] | 17:56 | |
| *** stetaylor [~stetaylor@2.223.131.74] has joined #baserock | 18:09 | |
| *** stetaylor [~stetaylor@2.223.131.74] has quit [Quit: Leaving...] | 18:31 | |
| *** flatmush [~flatmush@82-68-191-81.dsl.posilan.com] has quit [Quit: Leaving.] | 19:07 | |
| *** sambishop [~sambishop@95.144.14.182] has quit [Quit: Leaving] | 19:54 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!