-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows support #54
Comments
I was unsure whether the bug label is the most appropriate. Feel free to change as you see fit. |
Bug label is set automatically by the issue template. As I told, windows support is not a feature currently. So this issue should have been made as a feature request, using the proper template. |
Windows support for Pod::To::Cached has been fixed so I will close this for now. |
I'm taking another look myself, but it appears that I any way as I said I suspect there are other factors preventing Windows support in place. Should it persist, do you prefer opening a new issue or should I update here in case you want |
Please persist as much as you need. And while you're at it, there's a
number of issues in perl6/doc that need someone who works with Windows. If
you can fix a certain amount of them, we'd appreciate it
El mar., 23 jul. 2019 a las 20:52, Joel (<notifications@github.com>)
escribió:
… I'm taking another look myself, but it appears that Pod::To::Cached still
fails, I'll have to run a few
more scenarios on Windows before I can confirm it and open another issue
there (maybe have
somebody else confirm it to rule out that my windows setup is the cause).
I any way as I said I suspect there are other factors preventing Windows
support in place.
Should it persist, do you prefer opening a new issue or should I update
here in case you want
to reopen it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#54?email_source=notifications&email_token=AAAAD5BF3RG5HVYQIRMLT2LQA5HODA5CNFSM4IEPNVH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UCT3Y#issuecomment-514337263>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAAD5FBZX3QJOWOHXONYMDQA5HODANCNFSM4IEPNVHQ>
.
--
JJ
|
@JJ I will gladly take a look at them and see if I can provide some input if possible :) I have to add however that I am not a Windows user primarily so I'm not best suited in most cases |
Windows support is not longer a planned feature for this project, because of the numerous problems in the paths, so I will close this. |
We can't simply close this. As much as I don't use Windows, this is an essential module so we need Windows support for it. If the problem is in Pod::To::Cached, let's fix that. |
After |
This issue should mainly be viewed as a hub for discussion and information on this topic to determine the causes of Windows incompatibility, whether Windows support is desired and feasible (at this moment) and if so, how it could be achieved :)
If I can offer assistance I'd like to do so.
Describe the bug
Perl6::Documentable
can't be installed usingzef
due to failing tests onPod::To::Cached
.If tests are passed with
--force-test
, running examples will fail.To Reproduce
Installation error:
zef upgrade
zef update
zef nuke StoreDir
zef install ./Perl6-Documentable
Usage error:
zef install --force-test ./Perl6-Documentable
Error output
Attempting zef install:
When trying out example after forcing installation using
zef --force-test
:Desktop:
Additional context:
The installation error seems to happen due to
Pod::To::Cached
, while the usage error appearsto be mainly caused by the way paths are handled.
The text was updated successfully, but these errors were encountered: