Camelia, the Perl 6 bug

IRC log for #padre, 2012-12-05

| Channels | #padre index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
03:19 asarch joined #padre
04:58 Foxcool joined #padre
06:21 GlitchMr joined #padre
06:29 sewi joined #padre
08:27 sewi joined #padre
08:28 Kharec joined #padre
08:40 sugar joined #padre
09:05 dod joined #padre
09:12 dod joined #padre
09:27 rindolf joined #padre
09:38 feldmaus joined #padre
09:43 feldmaus joined #padre
11:55 dod joined #padre
11:58 Kharec joined #padre
12:22 bowtie joined #padre
12:51 Kharec joined #padre
14:35 kaare_ joined #padre
14:56 Kharec joined #padre
15:12 GlitchMr joined #padre
17:10 stkowski joined #padre
17:59 Kharec joined #padre
18:49 Di-ima joined #padre
21:24 El_Che bowtie?
21:25 bowtie El_Che, ??
21:26 El_Che do you know how to replace INC from the command line
21:26 El_Che replace, not append (-I)
21:27 El_Che I guess it's not possible
21:27 El_Che 1 failing test of having a modern perl on Solaris
21:28 bowtie do you mean that, thing that perlbrew dose to let you test against all installed perls, if so I only know perlbrew dose it
21:30 bowtie El_Che, is that not defined, you can see when you 'perl -V'
21:44 El_Che back
21:45 El_Che well, I know that :)
21:45 El_Che the thing I have is this
21:45 bowtie front :)
21:45 El_Che when running the test, the perl5db.t points to an module from a 5.10 install
21:45 El_Che instead of the one it's compiled against
21:45 El_Che trying to find out how the mixed up came
21:45 El_Che bbl
21:46 bowtie ok
21:46 sugar PERL5LIB?
21:46 mj41 bowtie: Hi. P::P::Git++
21:46 El_Che sugar: nope
21:46 sugar why?
21:46 mj41 bowtie++
21:46 El_Che thing is that the build/compile/test goes through an (m)gar wrapper
21:46 El_Che compiling by hand: fine
21:47 El_Che through this CSW build system: boom 1 test of 2500 :)
21:47 El_Che so there is an env setting somewhere
21:47 El_Che but there is no way a perl-agnostic build system would set a PERL5LIB
21:47 El_Che must be an include somewhere
21:47 sugar yep
21:48 bowtie mj41, cool, so I can progress the menu system to a dialogue then, is there any thing I have missed, remembering it is supposed to be a simple git interface
21:51 perlite_ joined #padre
21:53 mj41 bowtie: my daily git workflow is probably too complex ...  git gui (to select lines to stage), git ci -a --fixup anySHA, git rebase -i, git reset --hard, git co somebranch
21:54 mj41 bowtie: no branches yet? .... git co somebranch, git co -b somebranch
21:55 bowtie mj41, what version, I think v0.11 has stage/commit patch
21:55 botbot Welcome perlite
21:56 bowtie mj41, the intention was to be able to do a git commit and a github pull request
21:57 bowtie mj41, I do not want to try to replace -> git gui, git cola , gitg .....
21:57 mj41 bowtie: yes, but I would be great to have something more integrated to GUI ... something like 'git gui' to prepare commits
21:58 mj41 s/I/it/
21:58 mj41 bowtie: but not sure it is doable
21:59 mj41 something like select lines and right click to stage, unstage
22:00 bowtie mj41, O, but I could look at feeding an external app
22:01 bowtie with either current file or selection
22:03 El_Che my wife thinks I am crazy. I am doing the dish washer, weights, irc and compiling at the same time :)
22:03 El_Che she's right
22:03 mj41 there is + symbol next to line number ... maybe instead of green color there can be e.g. yellow for already staged lines/hunks
22:03 mj41 El_Che: :-)
22:03 bowtie mj41, when I go to a dialogue, we can then do some more branch stuff
22:05 bowtie El_Che, so you still have some spare capacity then to work out your Loads
22:05 El_Che she declared me cazy this noon when I went to a far away bike shop through the (light) snow to get my gears fixed :)
22:07 bowtie did you get winter tyres fitted?
22:07 mj41 bowtie: make sense. I can help with my use cases ... e.g. this stage/unstage and colors.
22:08 bowtie mj41, thanks, it's nice when I get some feedback and a kick ever once in a while
22:09 El_Che bowtie: no, thinking about it
22:09 El_Che bowtie: but winter is normally not so cold here
22:09 El_Che except last year
22:10 mj41 bowtie: yes, I hope I'm going to have some free time and energy now ... after a month of hard work ... separation of one big perl code repo to smaller parts and building rpms
22:11 bowtie as for the green +, to be yellow, I think that should be an enhancement for azawawi, as the vcs margin markers were developed against svn in first case, hence no stage/unstage support
22:12 bowtie El_Che, if I wanted to move the pp-git code to GitHub what is the procedure
22:13 El_Che bowtie: no idea
22:13 bowtie it just makes sense in this instance
22:13 bowtie neither have I
22:13 bowtie anybody else, know ?
22:16 bowtie in the same way the pp-mercurial should be in Mercurial
22:16 bowtie s/the/that/
22:19 mj41 bowtie: what about use of https://github.com/mj41/Padre and git filter-branch ?
22:20 mj41 bowtie: doing svn to git switch for the whole Padre is not easy https://github.com/mj41/padre-svn-git :-)
22:21 mj41 but I have some new experiences, so I can try again
22:21 bowtie mj41, it could, but my guess is that in 2008 people used the Padre server as it was free public space for plugins
22:23 mj41 bowtie: I know, probably each plugin should have own github repo
22:23 bowtie but there are issues, the lates plugin css-combe, last I locked the github was behind the initial cpan release
22:24 bowtie mj41, tell me about the community things like perl6 is every thing in one location,
22:27 bowtie the big problem is the cpan Pause access, for old and uncared for code
22:30 mj41 bowtie: Sorry, I need break/sleep now. We can continue tomorrow. ... I agreee, we need GitHub organization and separate repos. Then we can think about cpan :-).
22:31 bowtie mj41, night
22:31 mj41 night

| Channels | #padre index | Today | | Search | Google Search | Plain-Text | summary