Log file Viewer

[12:59:49] <iivvoo> how do I install a .tar.gz with builtdout?

[12:59:59] <iivvoo> I used to know but I forgot. and documentation is nowhere to be found, of course

[13:01:27] <mgedmin> there's a recipe called something.something.cmmi

[13:01:35] <mgedmin> cmmi stands for "configure; make; make install"

[13:01:39] <mgedmin> I've never used it

[13:02:25] <mgedmin> http://www.buildout.org/docs/recipelist.html tells me it's called zc.recipe.cmmi

[13:02:50] <iivvoo> it's not even a matter of make/make install, just the equiv of easy_install http://google-visualization-python.googlecode.com/files/gviz_api_py-1.8.2.tar.gz

[13:03:02] <iivvoo> I feel like I'm missing something trivial

[13:03:19] <mgedmin> oh, you want to install a Python package!

[13:03:23] <mgedmin> z3c.recipe.scripts

[13:36:39] <iivvoo> z3c.recipe.scripts "documentation" is giving me headaches

[15:29:10] <baijum> aclark: Hi !

[15:39:31] <aclark> baijum!

[15:39:51] <aclark> baijum: hey can you add me to the channel admins list so i can set the topic?

[15:40:21] <aclark> w00t

[15:40:34] <aclark> baijum: are you familiar with chanserv?

[15:40:42] <baijum> I run this command: /msg ChanServ FLAGS #buildout aclark +F

[15:40:46] <mgedmin> baijum! long time no see!

[15:40:56] <mgedmin> also, have you noticed that your twitter account seems to be hacked?

[15:41:05] <aclark> i think there is a way to add people so they can op themselves… cool thanks. that's what i was hoping for :-)

[15:41:10] <baijum> mgedmin: yeah. I just noticed :)

[15:41:23] <aclark> errr, let me see

[15:41:31] <mgedmin> good, I was worried something might've happened to you

[15:42:09] <aclark> baijum: ah ok you made me founder that probably works too thx

[15:42:51] <baijum> mgedmin: :)

[15:42:54] <mgedmin> we're gonna have a /topic!

[15:42:55] <aclark> !m baijum

[15:42:55] <pmxbot> you're doing good work, baijum!

[15:42:56] <mgedmin> yippee!

[15:43:09] <aclark> !m mgedmin

[15:43:09] <pmxbot> you're doing good work, mgedmin!

[15:43:11] <aclark> yep

[15:43:34] <aclark> probably a link to buildout.org to start

[15:43:52] <aclark> which is still on gocept IIUC

[15:44:10] <baijum> aclark: site moved to github ?

[15:44:58] <aclark> baijum: not yet it seems

[15:45:06] <aclark> probably still in the works if J1m wants to do it

[16:19:22] <J1m> aclark, I want to do it, but haven't had time to review your last iteration.

[16:19:45] <J1m> My main concern is that we don't regress and that the new update process is actually better than the old :)

[16:19:59] <aclark> J1m: yep

[16:22:27] <aclark> supton: welcome

[16:22:36] <supton> aclark!

[16:22:44] <aclark> supton: talking about moving docs to github at some point

[16:22:49] <supton> what's this buildout thing again?

[16:22:56] <aclark> heh

[16:23:02] <supton> +1

[16:23:18] <supton> do the same treatment as collective-docs, use RTD?

[16:28:25] <aclark> supton: probably just github-pages

[16:28:38] <aclark> supton: and actually, moo is moving that setup back to deus for some reason

[16:28:52] <aclark> something about RTD not supporting something or other

[16:30:04] <supton> aclark: meaning collective-docs will not be hosted on rtd anymore?

[16:31:37] <aclark> supton: yep, moving to developer.plone.org

[16:31:41] <aclark> supton: ask moo

[16:31:47] <aclark> i don't understand it, fully

[16:32:15] <supton> doesn't matter as long as the process for updating is the same

[16:32:49] <aclark> yep

[16:32:54] <aclark> i believe so

[16:32:55] <aclark> hah

[16:33:07] <aclark> i love the skull and crossbones: http://developer.plone.org/reference_manuals/old/old-style-vs-new-style/index.html

[16:34:15] <supton> ah, the things unicode has glyphs for

[16:34:44] <hannosch> <pile of poo> very important :)

[16:37:19] <aclark> hah

[17:08:27] <DanielHolth> Ever heard of buildout executing a part even though it is commented out / not in parts? My Plone buildout seems to be chmod'ing unexpectedly

[17:08:33] <DanielHolth> or chown

[17:09:20] <J1m> config parser comment syntax is funcky

[17:09:31] <J1m> funky

[17:09:41] <J1m> or maybe funcky ;)

[17:09:57] <DanielHolth> finunkcy

[17:10:07] <J1m> That's it.

[17:10:28] <aclark> J1m: apparently there was a regression from 1.4 to 1.5 such that inline comments no longer work, they must be ^ (at the beginning of the line)

[17:10:29] <J1m> buildout isn't likely to install a part it can't see. :)

[17:10:41] <aclark> related to configparser

[17:10:53] <J1m> aclark, are you talking about Python 1.4 to 1.5?

[17:11:23] <J1m> cuz buildout 1 just used config parser.

[17:12:13] <J1m> My next buildout 2 project is to simplify buildout config syntax, since buildout2 forked Python 2's config parser.

[17:12:38] <J1m> which will hopefully allow is to pin down the syntax much better.

[17:12:42] <aclark> J1m: no, buildout 1.4 to 1.5, but i could be wrong. supton said it worked in 1.4 and not 1.5…

[17:12:57] <J1m> I don't think so.

[17:12:57] <aclark> ah

[17:12:58] <aclark> cool

[17:13:09] <J1m> buildout 1 just used config parser.

[17:13:35] <aclark> well, in buildout 1 i know that has always annoyed me… not sure if it was a regression or for all time

[17:13:58] <J1m> inline comments for options is preoblematic, especially for buildout.

[17:14:07] <J1m> problematic

[17:14:10] <aclark> right

[17:14:26] <J1m> afaik, you can add comments after section headers.

[17:14:36] <aclark> but i think i've seen other software support it in their ini-style configs

[17:15:13] <J1m> Yeah, but other sw probably makes assumptions about option values that we can't, at least not now.

[17:15:35] <aclark> ideally i'd like: any line can have a comment any where

[17:15:36] <aclark> ah

[17:22:19] <supton> aclark: I was just saying that in 1.4, folks had EOL comments on things like versions.cfg, and they worked. I think there were some of these in older Zope2 or plone versions.cfg files at some point, but not on recent releases. When I started using 1.5 when plone was still on 1.4, I stripped these out of my own buildout

[17:23:14] <aclark> ah