Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-11-26

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

All times shown according to UTC.

Time Nick Message
00:11 stmuk_ also redpanda
02:49 ilbot3 joined #perl6-toolchain
02:49 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
05:11 TimToady joined #perl6-toolchain
06:23 domidumont joined #perl6-toolchain
06:28 domidumont joined #perl6-toolchain
07:52 ugexe `zef search HTTP` `===> Found 25 results` partial name matching on searches works again
08:21 stmuk_ ugexe++
08:25 stmuk_ would it also be possible to make zef install from a file such https://github.com/rakudo/star/blob/master/modules/MODULES.txt -- as a random example ;)
08:26 stmuk_ although I do wonder if using cpanfile format might be better
09:51 FROGGS joined #perl6-toolchain
11:14 domidumont joined #perl6-toolchain
12:10 nine tbrowder: actually it was in rakudo before the name racoon (which I'm still very fond of) came up
12:11 nine tbrowder: I'm currently a bit stuck on the question of how custom configure/build steps could be integrated.
12:20 tbrowder That's what I'm fooling around with. After initially giving up I am making some progress with bending the star config files. Problem at the moment is with zef's expectations.
12:22 tbrowder What I want is an installation in one site-wide subdir for root installation and forcing zef to use that subdir for all module installations by root. Other users can do their own thing if they want.
14:45 domidumont joined #perl6-toolchain
18:02 lizmat_ joined #perl6-toolchain
18:59 ugexe you can do that with zef already
19:00 ugexe tbrowder: ^
19:08 ugexe stmuk_: you can already do that by using the META6.json format, listing all the modules in `depends`, and then `zef --depsonly install META6.json`. It could easily be made to work with the format you showed, I'm just worried its not distinct enough to not cause problems determining other single-file formats
19:19 ugexe tbrowder: https://gist.github.com/anonymous/d84f82f7397fa60b4b81fcaa9f0eb5e3
19:25 ugexe ill add some ENV vars to set some of those things and make things easier soon
19:28 ugexe stmuk_: a cpanfile format would work better, but we'd probably want to tweak it to fit perl6 better (auth, how version ranges are declared)
19:30 ugexe which would work better than the META6.json + depends thing I mentioned, since `depends` will be skipped if they are found to be installed *anywhere* - whereas the requested modules (what you would type on the command line after `zef install ...`) will install to a --install-to target even if they are installed somewhere else already (as long that that somewhere else is not the --install-to target)
19:54 stmuk_ ok thanks I will experiment
19:55 stmuk_ actually R* should probably just use the same file as Task::Star (which currently needs updates anyway)
19:58 stmuk_ maybe I'll get tuits tomorrow
21:04 ranguard joined #perl6-toolchain
21:25 tbrowder ugexe: thanks for the gist. i'll have some questions later
21:35 ranguard joined #perl6-toolchain

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