01:35
frost joined
05:35
frost left
|
|||
jaguart | beginner question about ecosystem... docs.raku.org/language/faq#index-e...-ecosystem points us to apply for a PAUSE account and use CPAN - or should we be thinking about ``zef`` and ``fez``? If so, are there any docs for a ``zef`` newbie? | 07:07 | |
Also found: docs.raku.org/language/modules#Dis...ng_modules | 07:12 | ||
Nemokosch | zef is favored and the rest are becoming rather just fallbacks | 08:08 | |
Having said that, I don't know much about the usage either... | |||
08:27
ccntrq joined
08:37
frost joined
|
|||
CIAvash | jaguart: deathbykeystroke.com/articles/2021...et-started github.com/tony-o/raku-fez | 09:06 | |
09:17
dakkar joined
09:29
frost left
|
|||
lizmat | jaguart: good points! | 09:43 | |
Will make sure they mention fez, and update them further once github.com/Raku/problem-solving/issues/316 has been resolved | 09:46 | ||
Nemokosch | no ACTION? :c | 09:48 | |
10:09
frost joined
|
|||
lizmat | PRs for updates of those doc sections made :-) | 10:26 | |
jaguart++ # thanks for the nudge | |||
10:58
discord-raku-bot left,
discord-raku-bot joined
11:21
ccntrq1 joined
11:23
ccntrq left,
ccntrq1 is now known as ccntrq
13:00
discord-raku-bot left,
discord-raku-bot joined
13:39
frost left
14:20
ayu joined
14:23
ayu left
15:03
discord-raku-bot left,
discord-raku-bot joined
15:07
discord-raku-bot left,
discord-raku-bot joined
17:38
dakkar left
18:42
MasterDuke left
20:01
MasterDuke joined
20:42
ccntrq left
20:56
Guest1838 joined
21:04
ocomport left
|
|||
jaguart | Thanks for the pointers to zef... | 22:53 | |
So I'm reading what I can find... very basic question - assuming ZEF has a list of sources, how do I set up a zef server and add it into the sources so that I can install both public-global and private-local packages? | 22:59 | ||
lizmat | basically what you need is to set up a config for it: github.com/ugexe/zef/commit/9df58c...fba030c4fd shows how that was done for the REA | 23:03 | |
and then setup an endpoint that can serve the META required by zef: which is basically a JSON of the META's of the modules that you want to provide | 23:04 | ||
Jaguart | thank you 🙂 | ||
lizmat | perhaps I should add an option to Zef::Configuration for that :-) | ||
Jaguart | oh yes please 🙂 | ||
lizmat | ok, lemme do that tomorrow :-) | 23:05 | |
Jaguart | lizmat++ hero | 23:06 | |
Being able to use zef/fez to install private as well as public packages makes it much easier to get these and other raku ecosystems added to the corporate approved lists 🙂 | 23:10 | ||
and now starts to look at pointing fez to the local/private package server... | 23:12 | ||
lizmat | sleep& | 23:17 | |
Jaguart | hmm - which leads me to Naming... is there no pumpking for Raku ecosystem naming? | 23:22 | |
guifa | Jaguart: the :auth<foo> naming system sort of obviates naming clashes | 23:35 | |
I can have Utils:auth<me> and you can have Utils:auth<you> and as long as people say `use Utils:auth<someone>` there won't be any issues | 23:36 | ||
Jaguart | Yeah - I can see that, auth is like the vendor part of other env ecosystems | 23:38 | |
so is there any effort to come to a naming consensus - e.g. I've a small package I call PHP::Tiny -> being a nod to JSON::Tiny, but the Perlish equiv is PHP::Serialize | 23:39 | ||
actually, I use JAMD::PHP::Tiny - JAMD being myt Vendor equiv | 23:41 | ||
actually, I use JAMD::PHP::Tiny - JAMD being my Vendor equiv | 23:42 |