Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-01-25

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:50 ribasushi joined #perl6-toolchain
03:04 jdv79 i think we could structure that better, no?
03:45 ugexe everything else is already structured. it leaves 1 spot for an arbitrary structure of anything external tools might look at
07:29 domidumont joined #perl6-toolchain
07:32 FROGGS joined #perl6-toolchain
07:36 domidumont joined #perl6-toolchain
11:42 ilbot3 joined #perl6-toolchain
11:42 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
11:59 leont joined #perl6-toolchain
12:01 ranguard hi
12:04 ranguard https://raw.githubusercontent.com/perl6/ecosystem/master/META.list lists p6-Foo-v1.0.0 and p6-Foo-v1.2.0 - but http://modules.perl6.org/repo/Foo doesn't offer disambiguation  - discuss :)
12:05 * ranguard was actually looking for a senario of 2 authors having the same name'd module, rather  than same author with 2 versions
12:16 * flussence has a package on there with two versions of the same module inside, and afaik one just vanishes on install...
12:16 flussence seems like CURLI is the only part of the stack that takes module versioning seriously right now
12:18 ranguard and 2 'auth' releasing the same module name?
12:19 * ranguard still thinks it's madness
13:49 nine It's really hard to say in advance how this feature will play out in reality
14:11 jdv79 ranguard: what are you using modules.perl6 for?
15:02 ugexe i dont see any problems with auth/ver etc and multiple packages. if you consider `use Foo::Barr;` bar form and insist people be explicit ala `use Foo::Barr:auth<cpan:xxx>` its easier to digest
15:02 ugexe s/bar form/bad form/
15:15 lizmat and a new Perl 6 Weekly hits the Net: https://p6weekly.wordpress.com/2016/01/25/2016-123-what-are-we-waiting-4/
15:16 lizmat for some reason, some "f"'s are not rendering, although they *are* in the source
15:16 lizmat I blame wordpress JS madness
15:17 lizmat commute to AmsterdamX.pm meeting
15:17 lizmat &
15:18 lizmat oops ww  :-(
15:18 ranguard jdv79: an example of 2 authors releasing a module of the same name
15:19 ranguard nine: yea, that's part of my issue
15:21 ranguard ugexe: so I release Foo::Barr:authLLAP and everyone hard codes that, then I want to pass it on to someone else to maintain, now every has to update to Foo::Barr:authOTHER... OR I release everything with  a unique author that I can then pass on to someone else
15:22 ugexe see: s22 superedes, superceded_by, augments, excludes
15:23 ugexe https://design.perl6.org/S22.html#emulates (and the couple headings under it)
15:26 ranguard ugexe: so I run a bit of code on one box that has Foo::Barr:authLLAP.. it works, I deploy to a box with Foo::Barr:authOTHER that superedes Foo::Barr:authLLAP and shit breaks but I have to look through meta files to work out what's acutally being used?
15:26 ugexe the thing is they should also be putting the :ver<xxx> as well (not just the auth). so in most cases you would be hard coding *something*
15:26 ranguard or am I misunderstanding?
15:26 ugexe you can see which one is being used with RAKUDO_MODULE_DEBUG=1
15:27 ugexe but again, i think ver and auth should both be explicit if you want to avoid any type of auto-pick madness
15:28 ugexe i will say i dont think anyone has any idea how that aliasing will end up working
15:29 ranguard heh, all feels a bit too clever to me
15:30 ugexe the more time that passes, the more the things in s22 make sense to me
15:31 * ranguard hasn't got a big enough coffee mug to really process it, I guess I need to set some time asside to really review
15:31 ugexe so it might be overly clever for a reason (or stockholm syndrome has set in after a few years)
15:37 nine my first reaction was thinking over engineering, too, but then I came across use cases at work where a those power tools really would have been nice
15:38 nine S22 does come from experience with real world code bases.
15:40 ugexe yeah. s22 is over-engineered but i think its one area that may have to be
16:20 jdv79 i'm not convinced its clean enough but still working out why
16:46 leont joined #perl6-toolchain
17:26 Kassandry joined #perl6-toolchain
18:04 * b2gills .oO( Sometimes you have to over-engineer something to find the right level of engineering )
18:07 jdv79 grow it then trim it
18:11 FROGGS joined #perl6-toolchain
18:47 domidumont joined #perl6-toolchain
18:49 [Coke] b2gills: it's very hard to do only the right amount of work!
18:54 ugexe joined #perl6-toolchain
18:59 domidumont1 joined #perl6-toolchain
21:36 autarch joined #perl6-toolchain
22:52 leont joined #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary