Packaging of libraries

Daniel Dehennin daniel.dehennin at
Thu May 25 10:27:08 UTC 2017

Daniel Dehennin <daniel.dehennin at> writes:

I got some feedback from #perl6 IRC channel[1]

> Draw backs:


> - optimisation: pre-compilation can not take advantages of CPU features
>   since they are not known.

This one is not an argument as

    “any CPU-specific stuff will happen in the JITting of that bytecdoe”
    jnthn on IRC[2]

Some other discussion on IRC[3]:

    <nine> nebuchadnezzar: if there's no precomp file for the exact
    running rakudo, it will precompile transparently (except for the
    time required) and store the generated files in ~/.perl6 (most of
    the time)

    <nine> nebuchadnezzar: so multiple Perl 6 installations are not an
    issue for distributing precompiled files.

    <nebuchadnezzar> nine: ok, I'm not sure about the Debian policy for
    that point, I think we may want to avoid this step at run time for
    users, some of them may even not have a $HOME

I think it may be a key argument for our packaging policy, even if for

    “from my point of view, there's practially 0 reason to precomp on
    installation. It only has downsides.”





Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 357 bytes
Desc: not available
URL: <>

More information about the Pkg-rakudo-devel mailing list