Ah, that has been a mistake on my part, apologies. I can use a
more "correct" naming scheme in the future.
Are there any rules besides this one that release names should adhere
to? I'll write up a document about it so I have it documented, and
other people know what to expect as well.
On Wed, 6 N
This is not really zef's "implementation detail". See rakudo sources in
src/core.c/CompUnit and grep for 'sha1'.
Best regards,
Vadim Belman
> On Nov 6, 2019, at 9:04 AM, Patrick Spek via perl6-users
> wrote:
>
> The problem is clearly with the Linenoise module, I'll have to look
> into that a
When I report a problem, I try to supply as complete a picture as
possible, without imposing my filter on the data. So many times I've
had a vital clue omitted by someone who "didn't think that X was
important".
With so many parties involved, it's not surprising that errors reveal
issues entirely
The problem is clearly with the Linenoise module, I'll have to look
into that and see if it's something I can fix.
The path name you see is "an implementation detail" of Zef, I've been
told before. I have no clue how it actually calculates them, and no
idea where to find any documentation on that.
Normally a user is not supposed to see the hashed name. The reason for seeing
it is either an internal error or a problem with the path in the message. I
would rather tend to consider the latter and recommend checking existence of
the directories in the path and their permissions.
Best regards,
I'm treating this as a test of the process, reporting the problems
created, so that the process can be fixed. Merely hacking up a
solution might give me a better functioning installation, but it would
leave the problem for everyone else.
The unfriendly filenames are really an additional issue. Ord
In a previous installation location, have you tried grepping for:
"91857A0CE92503F53D56DEBB6F633402878D0FF0"
...and copying it over to your new 'dist' directory?
(/home/guru/rakudo/rakudo-star-2019.07.1/install/share/perl6/site/dist/)
The 'dist' directory appears to keep track of modules by versi
After a few difficulties caused by subtly different paths and version
identification (like -n vs .n for sub-version ids) the download and
installation appears to have worked, but trying the REPL produced the
following error message:
"I ran into a problem while trying to set up Linenoise: Failed to
Thank you Patrick!
On Tue, Nov 5, 2019 at 8:52 AM JJ Merelo wrote:
> Thanks a lot, Patrick.
>
> El mar., 5 nov. 2019 a las 14:28, Patrick Spek via perl6-users (<
> perl6-us...@perl.org>) escribió:
>
>> Hello everyone,
>>
>> I've seen people ask about 2019.07.1 in multiple avenues, myself
>> incl
Thanks a lot, Patrick.
El mar., 5 nov. 2019 a las 14:28, Patrick Spek via perl6-users (<
perl6-us...@perl.org>) escribió:
> Hello everyone,
>
> I've seen people ask about 2019.07.1 in multiple avenues, myself
> included. Since there was little response, I've set out to build it
> myself. The firs
10 matches
Mail list logo
