All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 02:09 | janet left #miro-hackers | |
| 06:40 | Jarrhead joined #miro-hackers | |
| 06:48 | IchEsseDichAuf joined #miro-hackers | |
| 06:52 | IchEsseDichAuf | where i can send a feature request? |
| 08:22 | maggie_s joined #miro-hackers | |
| 09:47 | SNAILBot joined #miro-hackers | |
| 09:47 | Topic for #miro-hackers is now Miro and MiroCommunity.org developers channel -- Got a bug? Have the ticket number ready. Nightlies at http://nightlies.pculture.org/ . | Channel is logged, "/msg SNAILBot help" for more info. | |
| 09:48 | zanoi joined #miro-hackers | |
| 10:34 | zanoi joined #miro-hackers | |
| 11:53 | kcw joined #miro-hackers | |
| 11:59 | willkg joined #miro-hackers | |
| 12:16 | willkg | hi! |
| 13:12 | deardiary: working on switching to gstreamer. | |
| 13:23 | bendk: you on? | |
| 13:52 | ajonas joined #miro-hackers | |
| 14:35 | bendk | hey willkg, I'm here |
| 14:36 | willkg | bendk: so... i continue to encounter dll hell. the ossbuild gstreamer packages are compiled against gtk 2.20.0 (i think). |
| 14:37 | bendk: so, we can use the ossbuild 0.10.6 packages and also update to gtk 2.20 which i'm not excited about.... | |
| 14:38 | or we could use the python all-in-one installer from bakhtiar which doesn't have good documentation for how it's built, but does use gtk 2.16. | |
| 14:38 | or we could use the OSSbuild stuff and compile our own packages using the bits we need. | |
| 14:39 | the problem with that is that they didn't document how the 0.10.6 packages are built anywhere i can find, there's no 0.10.6 tag in their repository (there are tags for 0.10.4 and 0.10.5) and it's not clear what rev it came from. | |
| 14:39 | plus it'll probably require some additional work to go off their beaten path. | |
| 14:40 | but they do seem to have good build infrastructure that's repeatable. | |
| 14:41 | i think the all-in-one option is the easiest if it works, but probably not maintainable going forward. | |
| 14:41 | building our own packages is more work right now, but probably more maintainable going forward. | |
| 14:41 | bendk | I like building our own if at all possible |
| 14:41 | I agree that it's way easier to maintain | |
| 14:42 | willkg | ok. |
| 14:43 | i'll start looking into how to build gstreamer packages. | |
| 14:59 | arpu joined #miro-hackers | |
| 15:11 | Odysimus joined #miro-hackers | |
| 15:13 | z3p joined #miro-hackers | |
| 15:14 | willkg | bendk: i have another interesting option: upgrade to python 2.7, use gtk 2.24, and gstreamer 0.10.7 beta 4 packages. i think that combination might work. |
| 15:15 | bendk: the only issue there is that i have to build libtorrent bindings for python 2.7. | |
| 15:15 | bendk | that sounds very interesting |
| 15:15 | that's probably easier than building gstreamer | |
| 15:15 | willkg | at first blush, it seems that way. |
| 15:18 | probably worth trying out. | |
| 15:22 | arpu joined #miro-hackers | |
| 15:41 | Odysimus joined #miro-hackers | |
| 17:43 | willkg | ok. i'm getting ready to tag v4.0.3 and do release builds. |
| 17:56 | bendk joined #miro-hackers | |
| 18:12 | uwe_ joined #miro-hackers | |
| 18:20 | willkg | bendk: i overhauled the release process page: http://develop.participatorycu[…]hp/ReleaseProcess |
| 18:20 | bendk: it should make more sense and be less scattered now. | |
| 18:20 | plus you could print it out and use it as a check list. | |
| 18:27 | mattjohnson joined #miro-hackers | |
| 20:54 | willkg | bugger... i forgot what i was doing. |
| 21:38 | oh, right. 4.0.3 builds ready to be tested. email sent. | |
| 21:42 | http://bluesock.org/~willg/blo[…]all_20110810.html | |
| 23:16 | CarlFK joined #miro-hackers |