|
Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec Set by moderator on 1 March 2016. |
|||
|
02:48
ilbot3 joined
|
|||
| moderator | Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec | ||
|
04:35
cognominal joined
06:50
domidumont joined
06:55
domidumont joined
10:46
cognominal joined
12:08
sufrostico joined
15:01
sufrostico joined
15:11
lizmat joined
16:12
hoelzro joined
16:14
flussenc1 joined
|
|||
| ugexe | anyone have a suggestions on how i can handle different content storages (p6c ecosystem, metacpan) via the command line? as additional storages can be added after install it can't just be hard coded names in the MAIN signature | 16:36 | |
| im wondering i should use an INIT to figure out at runtime a `short-name` attribute of each content storage (much like CUR), and then parse @*ARGS for --<short-name> or --/<short-name>, although these wouldnt be seen in the usage that shows command+args | 16:37 | ||
| llfourn | ugexe: you can write your own usage | 16:38 | |
| i'd say your just going to have to manually handle cli args and usage | 16:39 | ||
| ugexe | right, i do that. but it doesnt help when you do `script --not-an-arg` | ||
| llfourn | what do you mean? | 16:40 | |
| (I've never used @*ARGS before) | |||
| USAGE can be determined at runtime right so you can do whatever you like in it | 16:41 | ||
| ugexe | ill have to try with a sub named USAGE i think. ive been putting it in `MAIN(Bool :h($help)?)`, which gives me the custom usage for -h, --help, and 0 args, but the `<path> arg1 arg2\\n<path arg1 arg2` usage when i give an invalid argument | 16:42 | |
| llfourn | ah | 16:43 | |
|
17:13
domidumont joined
17:59
FROGGS joined
18:10
Kassandry joined
|
|||