Closed fluca1978 closed 4 years ago
This is fantastic. Honestly this command should be already doing this right? I didn't look at your code but are you using GetOpts or something also with like pod2usage so we can get "real" help output? Or MooX::Commander or something like that?
Umm... what do we gotta do to merge merge this? Let's get this going!
I've used Pod::Usage::pod2usage
to get this, but I don't know what's next since this PR has been opened 2 and half years ago.
I've used
Pod::Usage::pod2usage
to get this, but I don't know what's next since this PR has been opened 2 and half years ago.
I noticed that Rakubrew is being made, forked from this. A guy named @patrickbkr seems to be the primary maintainer... I'd love to continue working with him on it if he's going to take it seriously. It's listed as "the" Rakudo Environment Manager on the Raku website.
Yes, it is still listed as a way here https://rakudo.org/downloads, however I'm not sure about this because getting rakudo running is somehow very simple. However, if this project continues to grow, I will help merging my PRs.
@fluca1978: Actually this already happened. I have de-bitrotted and merged all of your PRs (a year ago or so). They just didn't end up in this repository, because I was in the middle of the huge refactor that resulted in rakubrew. I should probably close these PRs, now that rakubrew is close to release.
@fluca1978 @ispyhumanfly rakubrew is not officially released yet, but very very close. I'm currently only waiting for the latest binaries to be uploaded to the website before the "Everyone please test this!"-phase can start. Having more people involved in development is a good thing, so you're very welcome to get involved!
This PR was merged here. @fluca1978: Sorry for not communicating this earlier. Thanks for the work you put into this!
I implemented a first simple usage help command related to each subcommand. This makes implicit need for Pod::Usage. The idea is to document in specific pod sections each command and its attributes/arguments, so that the program can automatically display help for a single command. For instance:
rakudobrew help build
that is going to show the pod documentation for the build command. In the case no help command is required or the command is not found, the ordinary help is printed as already it is today. This allows to fix issue #91