#perlbrew — Public Fediverse posts

https://github.com/gugod/App-perlbrew/issues/877

Anyone fancy to see this idea come true ?

#perlbrew

https://github.com/gugod/App-perlbrew/wiki/End%E2%80%90to%E2%80%90end-(e2e)-testing-of-perlbrew

Some work-in-progress of making end-to-end tests better for #perlbrew

@FritzAdalis yes, but this isn't the sort of problem #perlbrew can help with as I was already using my own custom builds of #perl that don't go anywhere near the version of perl in /usr/bin.

雖然寫了 prompt() 的單元測試，但 e2e 測試要怎麼模擬出有人在前面按 Y 或 N ...

好像只能在 shell script 中靠類似這種方式:

yes | perlbrew ...
yes n | perlbrew ...
echo | perlbrew ...

#perlbrew

https://github.com/gugod/App-perlbrew/pull/856

#perlbrew

#perl

open my $in, '<' \$str;
open my $out, '>', \$str;

我記得這語法在很舊的 perl 是不管用的，但我應該不必擔心（吧）

https://github.com/gugod/App-perlbrew/issues/843

來試着把 `ExtUtils::MakeMaker` 這個 dependency 拔掉好了。

#perlbrew
#coscup

https://metacpan.org/release/GUGOD/App-perlbrew-1.02

It's there, perlbrew 1.02.

#perl #cpan #perlbrew

@ferki @verzulli If I understand your requirements correctly, you could install a #perl version with #perlbrew on your local machine, install your required modules with #cpanm and provided libraries match between your dev and prod machines you can just copy the perl directory and run the perl with full path in the new location.
If there is a library mismatch you are in a bit of pain to get it to work no matter what you do.
May I suggest you build the restapi with #mojolicious?

https://github.com/gugod/App-perlbrew/actions/runs/13212861754

Working on running simple end-to-end tests for #perlbrew that is just building #perl on commonly used Linux distributions.

Couldn't figure out why the test htmldir3.t failed only on #RockyLinux but not on other linux distributions.

I'm willing to bet that a few packages needs to be present, but not sure what that might be.

https://github.com/gugod/App-perlbrew/actions/runs/13100409688/job/36547979805

Any cygwin users ?

I'm trying to run perlbrew tests on cygwin on GitHub Action. Most of the setup worked but it ended up with this error of missing `crypt.h` when installing dependencies. Module::Build::Tiny in this case, but perhaps there will be more.

If you know how this can be resolved or avoided, please help!

#perlbrew
#perl
#cygwin

https://github.com/gugod/App-perlbrew/pull/836/files#diff-e6e17f54de1ce7310b46c141a9efe74bc4b9a76b0fa1ad9e8064d576db6574bd

用 #yamlscript 把 #perlbrew 的一部分 CI workflow 檔案重新整理一下了。我覺得很好。

做 perlbrew 以來，一直覺得必須要提供夠充分的文件來給眾多指令提供說明。於是一開始就有做 `perlbrew help <CMD>` 這種方便讓人查 CMD 用法的 `help` 指令...

但都這麼多年了，今天我才發現 `help` 本身沒有文件。也就是 `perlbrew help help` 只會印出「找不到文件」。

這真是太糟糕了啊！

#perlbrew

( 有人要送 PR 來嗎 ? => https://github.com/gugod/App-perlbrew/ )

https://hackmd.io/@gugod/rkPZyOotA#/

平平順順的講完了，很好！

#yapcjapan
#perlbrew

https://github.com/G4Vi/Perl-Dist-APPerl/releases

It seems trivial to let #perlbrew to support the installation of APPerl releases -- because it is trivial to install those release -- essentially you just `curl + chmod +x` !

perlbrew 1.00 is now on CPAN.

I've aggregated my thoughts and make a special note for this release.

https://perlbrew.pl/Perlbrew-1.00.html

This release is dedicated to #osdctw and will be briefly presented in YAPC::Hakotadate, tomorrow (2024/10/5).

#perlbrew
#yapcjapan

#perlbrew mascots made by Bing Copilot (Dall-E 3)

太可愛了必須放進投影片理面

@ology @profoundlynerdy @bololacertus @overeducatedredneck @fuzzix I’ve found most people use #perlbrew because they explicitly want a repeatable #Perl environment with a contained installation and modules. They don't need it just to get any random Perl application to work.

@profoundlynerdy @bololacertus @overeducatedredneck @fuzzix It’s not necessary for most because the #Perl culture gives a damn about not wasting users’ time while still moving the language forward: https://fosstodon.org/@leonerd/111856552091954510

Some more @leonerd posts from the same thread:
https://fosstodon.org/@leonerd/111852567952393719
https://fosstodon.org/@leonerd/111855908131666259
https://fosstodon.org/@leonerd/111856356366461768

If you must have multiple Perls, #perlbrew is simple and common: https://perlbrew.pl

@ChristosArgyrop @leonerd @pjakobs #!/usr/bin/env perl

is the typical way to call whatever #perl happens to be first in your environment's path

The nice thing about #asdf is it reads a `.tool-versions` file in a given project's directory and will use the specified perl, ruby, node, whatever version via its shim scripts: https://asdf-vm.com/guide/getting-started.html#_6-set-a-version

I used to use #plenv, which is like #perlbrew plus asdf but for Perl only: https://github.com/tokuhirom/plenv

Just gained 5 GB of disk space by running perlbrew clean. Didn't know I had this many old build directories hanging around.
#perl #perlbrew

@funkatron
@Perl Someday I should write up how I manage #Perl projects with #asdf and #direnv. Everyone talks about #perlbrew and sometimes #plenv, but it’s nice to have a single way to manage local project environments for any #programming language, especially when the project has a stack of languages and runtimes that you want to specify in one place.

#perl protip: If you're trying to build an older perl (say, 5.10.1) with #perlbrew and you're getting weird errors involving unicore, you want to unset the PERL_UNICODE environment variable. That should fix it.

@ovid @fuzzix (#ActiveState’s solution is a *little* more involved than that because it spins up project-specific language environments. So it’s more like #Carton + #perlbrew in the #Perl world.)

@lolzac @ramsey @dmnelson @scriptingosx Oddly, #Apple has not been terrible in keeping #perl somewhat recent on #macOS: #Ventura ships with v5.30.3 from 2020.

But most advise not messing with an OS or distro’s system runtimes, especially if you want to install or upgrade libraries and modules from #CPAN etc.

The two main Perl solutions are #perlbrew: http://perlbrew.pl

And #plenv (used to be my fave): https://github.com/tokuhirom/plenv

@rrwo @profoundlynerdy @leonerd I’ve never heard of any *other* language ecosystem supporting multiple package branches at scale. Doesn't mean it can't or shouldn't be done, though, for the reasons you mention.

Now that we have quite a number of years’ experience with #perlbrew, #plenv, and #Docker #containers under our belt, adapting the #Perl toolchain and #CPAN to support multiple release branches sounds like an interesting project.