You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we don't have any documentation leading to the usage of pulsar in the CLI. And the closest thing we have is the archived atom documentation which can be confusing for users.
So we will likely want to take a look at adding this page.
I'm looking at tackling hacking-pulsar in general as not much has been done on this and is our major "missing chapter" - a lot of it really hinged on some design decisions like what binaries we would support and if ppm was going to be replaced with pulsar -p.
I'll have a look at doing this in the next couple of days.
I'm looking at tackling hacking-pulsar in general as not much has been done on this and is our major "missing chapter" - a lot of it really hinged on some design decisions like what binaries we would support and if ppm was going to be replaced with pulsar -p. I'll have a look at doing this in the next couple of days.
Ah that makes sense then on why you've taken some time before starting. I think for now it seems pretty cemented that pulsar -p will be used going forward. But otherwise would it make sense to defer the supported systems to our download page? Since I imagine that will be subject to change sooner rather than later?
Yeah I think the installation section will be sparse with mostly just a link to the download page. It is really meant for repo installations involving PPAs or more complicated installations.
Have you checked for existing feature requests?
Summary
Currently we don't have any documentation leading to the usage of
pulsar
in the CLI. And the closest thing we have is the archived atom documentation which can be confusing for users.So we will likely want to take a look at adding this page.
Reference
Enter your response below:
More clear documentation for users.
Any alternatives?
N/A
Other examples:
No response
The text was updated successfully, but these errors were encountered: