Perl 6 - the future is here, just unevenly distributed

IRC log for #pr-challenge, 2015-01-09

| Channels | #pr-challenge index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:02 vroom joined #pr-challenge
00:11 lbrown_ joined #pr-challenge
00:12 jashank_ joined #pr-challenge
00:12 fuzzix joined #pr-challenge
00:12 vroom joined #pr-challenge
00:12 jkg joined #pr-challenge
00:12 oeuftete joined #pr-challenge
00:12 ohoushyar joined #pr-challenge
00:12 pink_mist joined #pr-challenge
00:12 Su-Shee joined #pr-challenge
00:12 memeticpox joined #pr-challenge
00:13 trs joined #pr-challenge
00:14 dams joined #pr-challenge
00:14 heytitle joined #pr-challenge
00:14 bentglasstube joined #pr-challenge
00:15 jb360 joined #pr-challenge
00:15 dolmen joined #pr-challenge
00:18 sawyer joined #pr-challenge
00:18 eam joined #pr-challenge
00:18 rnewsham joined #pr-challenge
00:18 tbushell joined #pr-challenge
00:18 estrabd joined #pr-challenge
00:18 michael joined #pr-challenge
00:19 btyler joined #pr-challenge
00:19 hernan604 joined #pr-challenge
00:20 mcsnolte joined #pr-challenge
00:24 sivoais joined #pr-challenge
00:31 exhortatory joined #pr-challenge
00:56 manchicken joined #pr-challenge
01:08 tinypig joined #pr-challenge
01:22 vroom joined #pr-challenge
01:54 vroom joined #pr-challenge
02:05 Su-Shee_ joined #pr-challenge
02:28 vroom joined #pr-challenge
02:39 absolut_todd joined #pr-challenge
03:02 jevin joined #pr-challenge
03:08 boreas joined #pr-challenge
03:36 manchicken joined #pr-challenge
03:39 vroom joined #pr-challenge
03:50 ivanwills joined #pr-challenge
03:54 bambams joined #pr-challenge
04:59 veryrusty joined #pr-challenge
05:01 oalders joined #pr-challenge
05:14 BRAD_ joined #pr-challenge
05:23 boreas joined #pr-challenge
05:55 ivanwills joined #pr-challenge
07:12 boreas joined #pr-challenge
07:31 nbezzala joined #pr-challenge
07:34 boreas joined #pr-challenge
07:34 panshin joined #pr-challenge
08:04 neilb joined #pr-challenge
08:09 nbezzala there are 21 test files in the t/ directory, but when I run perl -Ilib t/* it only runs 3 tests
08:09 neilb joined #pr-challenge
08:09 nbezzala why?
08:10 nbezzala I mean, it's just running the 3 tests in the first file
08:10 nbezzala maybe I should use prove
08:10 nbezzala ah, yes. thats better
08:11 moritz nbezzala: because perl <script> <more args> passes the <more args> as arguments to the first <script>
08:11 moritz nbezzala: I'm surprised it runs three of them at all
08:11 nbezzala sorry, the first file had 3 tests. I thought it ran 3 files
08:11 moritz ah
08:12 moritz now things make sense again
08:12 nbezzala but not to me
08:12 nbezzala supposing there are two files 1.t and 2.t
08:13 nbezzala and I say perl *.t
08:13 nbezzala does it translate to perl 1.t 2.t
08:14 moritz yes
08:14 moritz you can try by running 'echo perl t/*.t'
08:14 moritz that will print the command line after shell expansions, instead of executing it
08:17 nbezzala oh, ok. Thanks moritz
08:18 nbezzala http://nbezzala.blogspot.co.nz/2015/01/how-to-make-your-first-contribution-to.html
08:21 moritz nbezzala: btw you can also run   perl Build.PL; ./Build test
08:22 moritz nbezzala: which will also check if all dependencies are installed
08:23 nbezzala moritz: thanks. I'll update the blog post. Should I say, "If there is a Build.pl, then...."
08:29 bjakubski joined #pr-challenge
08:29 nbezzala ok, changed it
08:31 moritz if there's a Build.PL, run perl Build.PL; ./Build test  if there is Makefile.PL, run  perl Makefile.PL; make test
08:31 moritz that's the two competing standard build systems for perl modules (simplifying here...)
08:31 sue joined #pr-challenge
08:32 moritz if there's a dist.ini, run 'dzil test' (and install Dist::Zilla first, if not installed yet)
08:38 nbezzala ok
08:56 neilb joined #pr-challenge
09:00 nbezzala guess my next task is to write a regexp to match either '2 weeks 3 days' or '3 days 2 weeks' . I'll do that tomorrow
09:05 Relequestual joined #pr-challenge
09:12 shorty_mu joined #pr-challenge
09:30 neilb joined #pr-challenge
10:02 ivanwills joined #pr-challenge
10:16 sue joined #pr-challenge
10:20 mvuets joined #pr-challenge
11:12 veryrusty joined #pr-challenge
12:08 panshin joined #pr-challenge
13:11 vroom joined #pr-challenge
13:18 vroom joined #pr-challenge
13:20 panshin joined #pr-challenge
14:09 neilb So far no signups today…
14:12 neilb But getting completions now \o/
14:14 manchicken joined #pr-challenge
14:51 fuzzix joined #pr-challenge
14:58 ambs \o/
15:01 neilb Suggestions for a good *beginner* tutorial on git and github? Just the basics, leading up to Sawyer’s “doing a PR” guide?
15:03 thrig hmm. "Pro Git" is probably overkill
15:03 Relequestual what about try git? https://try.github.io
15:04 ambs Relequestual++
15:04 mvuets maybe https://help.github.com/categories/bootcamp/
15:04 mvuets as it's tied to what we do - pull requests via github
15:04 Relequestual personally I found the web version of pro git to be useful http://git-scm.com/doc
15:05 Relequestual mvuets I don't think that covers how git works though =/
15:06 Relequestual setup, create, fork... nothing about commit, pull, push, that I can see anyway
15:06 pink_mist hmm, what happened to everyone being opped? heh
15:06 mvuets fwiw it has a page https://help.github.com/articles/good-resources-for-learning-git-and-github/
15:06 pink_mist oh thanks thrig :P
15:06 Relequestual pink_mist good question, but probably for the best
15:07 pink_mist I noticed sawyer was opping everyone, so let's make sure he still has op :P
15:08 pink_mist https://guides.github.com/introduction/flow/index.html this is an interesting help resource too
15:08 thrig and also http://justinhileman.info/article/git-pretty/full/
15:10 oalders not for beginners, but interesting test of git skills: https://github.com/hgarc014/git-game
15:10 Mithaldu there's only one thing to really lean about git: if you don't rebase your branches you're making maintainership for other people hell
15:11 tinypig joined #pr-challenge
15:13 Relequestual pink_mist you could extend that to all of https://guides.github.com
15:14 pink_mist true, but I wanted something specifically useful for the challenge; everything on that site is a bit much to take in at once
15:20 mvuets https://www.youtube.com/watch?v=1ffBJ4sVUb4 <- another nice demo on understanding required git internals
15:26 sromanov joined #pr-challenge
15:46 pink_mist hmm, that git game was fun, oalders ... but I seem to have missed parts of it -- in the conclusion it talks about having removed tags ... I didn't need to do that at all
15:48 neilb *bzzzt* thank you for playing pink_mist!
15:50 ambs :D
15:53 jluis joined #pr-challenge
15:53 oalders i haven't finished it yet, just found it this morning.  it would be good if the steps in the README were numbered so you know if you've gone in the right order
16:25 Su-Shee just use git like cvs at the beginning and don't waste more time than 5 minutes on it and another 5 minutes on github itself...
16:26 thrig I can do rcs in any vcs
16:45 sromanov joined #pr-challenge
16:49 jluis joined #pr-challenge
17:30 neilb joined #pr-challenge
17:51 panshin joined #pr-challenge
18:01 panshin joined #pr-challenge
18:17 daveh neil, made a small step forward with the map, will do more after I do my accounts
18:22 ohoushyar Hello everyone
18:23 daveh neilb: even
18:23 neilb daveh: cool!
18:25 ohoushyar I'm going to change WebService::MusicBrainz to use the lates version of musicbrainz API.
18:26 ohoushyar What is important about backward compatibility which I need to care?
18:26 thrig any reverse deps of the module?
18:26 ohoushyar Shall I take care of it?
18:26 ohoushyar According to kwalitee there is one dist which using it currently
18:27 thrig two! https://metacpan.org/requires/distribution/WebService-MusicBrainz?sort=[[2,1]]
18:31 mvuets joined #pr-challenge
18:42 ohoushyar exactly two
18:44 trs ohoushyar: keep in mind there may be lots of things using it that aren't CPAN.
18:45 thrig right, scripts and such
18:47 trs indeed.
18:47 trs in particular because it's the kind of thing one would use most often in scripts and such.
18:48 ohoushyar trs: yeah that's what I was thiking as well
18:49 ohoushyar So here is my plan
18:49 ohoushyar Keep the existing code work as it was
18:50 ohoushyar add an option in init part to accept API version
18:50 ohoushyar I just not sure previous version should be default or new one
18:51 ohoushyar If I want to keep it as it was then I need to put first version as default value
18:52 ohoushyar and then of course depends on the version implementaion would different
18:54 ohoushyar I can use environement variable as well ...
18:55 thrig or just do the new version in ::V2.pm or something? how much overlap is there?
18:58 ohoushyar few enteries changed
18:59 ohoushyar the rest are mostly same as before
18:59 ohoushyar I'd say not quite different
18:59 thrig ->new(api => 2) then?
19:01 ohoushyar then for changed entries check api and do differently
19:01 ohoushyar or call another method
19:01 ohoushyar something like that
19:03 trs how much does the Perl API need to change?
19:03 trs i.e. the thing that scripts and other Perl code use
19:03 trs if not much, then a pattern like ->new(api => 2) seems reasonable.
19:03 trs and it'll affect just the backend, like you said.
19:04 trs + the few frontend stuff that changes
19:04 ohoushyar correct
19:07 ohoushyar and also version 1 is depricated
19:12 ohoushyar so I'll keep the default version as 1
19:13 ohoushyar I don't want to break other dists
19:13 pink_mist you could perhaps do something like _trying_ version 1 by default, and if it doesn't work, seamlessly switch to v2?
19:14 pink_mist while still keeping the module's api the same (if that's feasible)
19:14 ohoushyar pink_mist: can you explain more?
19:15 pink_mist I think I'd haveto look into it more than I'm willing to do right now to see if what I'm saying is even feasible, so not really :P
19:16 ohoushyar :)
19:22 sue joined #pr-challenge
19:29 vairav joined #pr-challenge
19:32 sawyer pink_mist: idon't know how i lost op, but thanks :)
19:32 pink_mist half of the network got disconnected a day or two ago =)
19:32 sawyer oh :)
19:34 bjakubski joined #pr-challenge
19:48 monsieurp SUP
19:48 trs sawyer: register with chanserv?
20:04 mstr joined #pr-challenge
20:06 mvuets cool, my 2nd pr just got merged (-:
20:06 mvuets gonna work on the 3rd one now
20:10 sromanov joined #pr-challenge
20:27 neilb mvuets++
20:30 mstr the more you read (not necessarily equals to "know") about git the more you start questioning your own capabilities.. who's with me? :)
20:30 mstr quick question
20:30 mstr a PR on github is based on a published branch of my fork
20:30 mstr and i can commit as much as i want to on this branch even after the PR is created
20:31 mstr i can even rebase
20:31 mstr one of my PRs even got merged after i rebased to fix up some stuff
20:31 mstr but here's the question: isn't rule #1 not to rebase a published branch?
20:32 jrhunt not precisely
20:32 jrhunt rule #1 is to not rebase something other people have seen, or have a direct reference too
20:32 thrig depends, are those affected angry enough to form a mob that can reach you?
20:32 jrhunt and even that is more of a guideline
20:32 vairav joined #pr-challenge
20:33 mstr well of course, since nobody branched off of my branch it might not be a big deal
20:33 jrhunt the PR is more like "go merge the branch named X on approval"
20:33 jrhunt and less of "merge commits A, B and C"
20:33 jrhunt so there is no referential problem
20:33 jrhunt the real problem with rebase is when you push a branch, I pull it, and then you rewrite history
20:33 mstr AH. ok. that explains a lot then.
20:33 jrhunt i have copies of things that don't exist
20:33 jrhunt the same problems apply to out-of-stream time travel
20:33 jrhunt :D
20:34 mstr so if somebody forked my repo (with has a branch X open at the time), and afterwards i would rebase that branch - then this dude would be in trouble
20:34 mstr once he does another pull
20:35 jrhunt not quite
20:35 jrhunt since github "forking" is really a clone of master, where origin = your repo
20:35 jrhunt if you rebase branch after he forks, then yes, there will be problems
20:35 jrhunt err.. master. not branch
20:36 jrhunt if you rebase master
20:36 jrhunt i rebase feature branches all the time
20:36 jrhunt we even wrote a code review tool that can handle that
20:36 jrhunt (at $work)
20:37 mstr well but if somebody clones my repo all branches are cloned right? so if i rebase once of these branches after he forked my repo and he would want to pull from upstream/branch (my repo) there would be problems
20:38 mstr but ok, now it seems too constructed of a problem for me to care :)
20:38 mstr plus, serves them right.. that'll teach 'em not to fork my repos ;)
20:39 mstr another quick question. i cannot set an alias called "log" to change default behaviour (because of yeah, well, whatever, scripts depending on it maybe)
20:40 mstr i meant "status" in this example
20:40 jrhunt i tend to use abbreviated forms for aliases
20:40 mstr yet i can change the behaviour by setting a config group "status" and switching some settings effectively changing the default behaviour.
20:41 jrhunt `git lg` is a custom log formatter with a -n 40, --pretty, etc.
20:41 jrhunt `git st` is a custom form of status that I forget the specifics of atm
20:41 mstr seems to me that the at least the reasoning is flawed.
20:42 jrhunt what if you could make `git status` an alias for `git reset --hard HEAD`?
20:42 mstr damn it. :)
20:42 jrhunt instead of seeing what had changed, you effectively blow away your working copy changes!
20:42 jrhunt that's the rationale
20:43 mstr fine. then this should be the documented reason. not some excuse about scripts expecting exactly that format of output
20:44 jrhunt that too
20:44 jrhunt although i think that reasoning goes beyond just `git status`
20:44 jrhunt and every time i've had to automate git processes, i stick to the plumbing side of the house
20:44 mstr well i used that example because you can slap a "...
20:44 mstr [status]
20:44 jrhunt porcelain is too ... breakable
20:44 mstr short=1
20:45 mstr into your .gitconfig and change the output format of "git status"
20:46 jrhunt what about `git status --porcelain`?
20:46 jrhunt does it affect that?
20:49 mstr no. just as documented.
20:52 mstr oh, and btw.. thanks neilb... because of you i actually have to work now. :) wanted to do some simple PRs and ended up with co-maint of my first cpan distribution
20:53 neilb mstr: \o/
20:53 mstr who has some good links on how to easily turn a git repo into a proper zip or whatever the format is i have to upload to cpan?
20:54 mstr maybe a "CPAN for dummies" link would be appropriate
20:54 neilb what’s your dist?
21:12 mstr module::install::repository
21:17 neilb to build a tarball: perl Makefile.PL
21:17 neilb then: make dist
21:18 daveh neilb: i even did more JavaScript today!
21:19 neilb this is meant to be a Perl challenge, try to remember :-)
21:20 rjbs There are some non-Perl dists on the CPAN…
21:21 mvuets how come?
21:21 rjbs Because people uploaded them!
21:22 mvuets d'oh
21:22 mvuets what for? (-:
21:22 rjbs to share!
21:22 rjbs example, http://search.cpan.org/~avar/Test.php-0.13/Test.php
21:22 mvuets ah, that guy
21:23 daveh nailb: perl is dead
21:23 daveh neilb even
21:24 mvuets rjbs: interesting! a php lib with a perl installer
21:24 mvuets perl++
21:37 jrhunt oooo
21:37 jrhunt anyhow, i blogged about my January experience so far
21:37 jrhunt http://jameshunt.us/writings/cpanpr-2015-jan.html
21:38 mvuets jrhunt++
21:38 mvuets how do we aggregate all such posts?
21:38 jrhunt so few of the "what to do when its not obvious what to do" suggestions don't apply to purely XS modules
21:38 jrhunt i was going to post the link to twitter, under #cpanpr
21:38 mvuets jrhunt: tag it "cpanpr" (-;
21:39 * mvuets . o O ( cpanpr-planet.org )
21:39 elmerq joined #pr-challenge
21:39 jrhunt im no twitter expert; when you say 'tag it "cpanpr"', is that different than using the hashtag #cpanpr?
21:40 Su-Shee no
21:41 mvuets jrhunt: oh, sorry. i meant in your blog. so google/ddg/etc could index it - more odds when search for "cpanpr" it will pop up in search results
21:42 jrhunt ah.  my blog doesnt support tags
21:42 jrhunt by design
21:43 mstr just finished the git-game somebody linked today
21:43 mvuets jrhunt: no problem. google likely wouldn't core for that anyways. it cares for text. it could work if you mentioned "cpanpr" in your text, title, side notes, category, whatnot
21:43 mstr but either i cheated without knowing or i never had issues with branches/tags being the same name
21:45 mstr also, found two bugs (running the whole thing on os x)
21:45 mstr PR anyone?
21:45 jrhunt mstr: you should have someone CPANify it first
21:45 mstr :)
21:45 jrhunt then have neilb add it to Feb's line-up
21:45 jrhunt and then, hope.
21:47 mstr neilb: thanks.
21:54 veryrusty joined #pr-challenge
21:59 manchicken_ joined #pr-challenge
22:03 mstr joined #pr-challenge
22:07 daveh mstr: Dist::Zilla make cpanifying and releasing easy. in the early stages of learning
22:08 daveh how are we getting on with blogs.perl.org?
22:08 athos joined #pr-challenge
22:09 neilb daveh: I’m collecting a list of people who want a blog.
22:09 neilb I’ll email aristotle a CSV on Sunday
22:09 daveh am i on that list? I think I mails you
22:10 daveh mailed
22:10 neilb i think you mails me too
22:10 neilb :-)
22:11 vairav joined #pr-challenge
22:12 * daveh &
22:18 boreas joined #pr-challenge
22:18 elmerq left #pr-challenge
22:21 mstr neilb: make dist complains about the MANIFEST (which i had nothing to do with), and a make manifest doesn't fix it. where could i read about the whole meaning of that "inc/" folder?
22:22 neilb your best best is to ask in the #toolchain channel
22:23 neilb mstr: it uses Module::Install which I’m not really familiar with
22:23 neilb what’s the complaint you get?
22:23 mstr It appears that your MANIFEST does not contain the same components that
22:23 mstr are currently in the 'inc' directory.
22:23 mstr Please try running 'make manifest' and then run 'make dist' again.
22:24 mstr that last helpful advice of "make manifest" doesn't fix anything
22:24 mstr i found a .shipit file in the repo. seems that the original author uses some tool to prepare everything?
22:25 mstr now of course i could switch it to dist::zilla but seeing as this module is a plugin to module::install i feel the mob a-coming
22:26 PerlJam mstr: https://metacpan.org/source/MIYAGAWA/ShipIt-0.60 btw (if that helps)
22:33 mstr oh my. self referencing much? starting with my assigned dist Plack::Middleware::DoCoMoGUID -> uses module::install::repository -> some more PR in that dist -> instead of a merged PR i get co-maint -> somehow ending up with shipit.
22:34 thrig "this deal keeps on getting worse" as Imperial agents descend on cloud city
22:37 mstr oh yeah... and in the meantime of course i had to use perlbrew (because yes). of course that has bugs too. so checking sources everywhere, all the while learning git from the ground up. that one-PR-a-month challenge is testing my faith in oss ;-)
22:42 mstr i'm off. most probably having nightmares about detached HEADs :)
23:03 veryrusty joined #pr-challenge
23:23 choroba joined #pr-challenge
23:43 vairav joined #pr-challenge

| Channels | #pr-challenge index | Today | | Search | Google Search | Plain-Text | summary