Re: changing name of module
On Sun, Jun 07, 2020 at 02:28:08PM +0100, Richard Hainsworth wrote: > On 07/06/2020 13:31, Parrot Raiser wrote: > > Create an updated version, perhaps with an "rk" prefix, (preserving > > any text alignment, since "p6" and "rk" are the same length), then > > change the "pk" version simply to invoke the "rk"? > > > > Existing code should continue to work, albeit nanoseconds slower, > > while new code can be culturally consistent. > > Why nanoseconds slower? (I won't notice them, but why would a name change > slow things?) > > If alignment is not a concern, then p6 and raku are equivalent? I believe the idea is that two modules are installed on the user's machine: the renamed rk-* one and a single-line p6-* shim that only imports the rk-* one. Thus, other programs that use the p6-* name will load that first, then load the rk-* one, hence the nanoseconds delay. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Re: changing name of module
Why nanoseconds slower? (I won't notice them, but why would a name change slow things?) If alignment is not a concern, then p6 and raku are equivalent? On 07/06/2020 13:31, Parrot Raiser wrote: Create an updated version, perhaps with an "rk" prefix, (preserving any text alignment, since "p6" and "rk" are the same length), then change the "pk" version simply to invoke the "rk"? Existing code should continue to work, albeit nanoseconds slower, while new code can be culturally consistent.
Re: changing name of module
Create an updated version, perhaps with an "rk" prefix, (preserving any text alignment, since "p6" and "rk" are the same length), then change the "pk" version simply to invoke the "rk"? Existing code should continue to work, albeit nanoseconds slower, while new code can be culturally consistent.
changing name of module
Hi, I've written some modules and released them into the Ecosystem. (I don't use cpan for raku) In the past, I have named my modules 'p6-xxx'. So references for zef would be git - finanalyst - p6-xxx (loosely speaking). Now I am considering whether to rename the module to `raku-xxx` There are three alternatives: a) leave the module name as before - historical roots. b) change the name in my github repo, and change the source reference in the public ecosystem file (https://github.com/Raku/ecosystem/blob/master/META.list). I don't know what would happen if someone has installed the module using zef, and the source changes. c) leave the old versions of the module with one source, create a new repo and bump the version number in the META.json file Any comments about what might be best practice? Regards, Richard
