Active perl
Author: o | 2025-04-24
Perl Production-ready, under active development Perl 5.40.1 is the current stable version of Perl. Perl is actively maintained and developed (git repository) by a large group of dedicated
active perl strawberry perl - PerlMonks
P4Perl- Perl Extensions to the Perforce API IntroductionSo what's P4Perl about? In a nutshell P4Perl is the product name for a Perl module that allows you to execute Perforce commands without leaving Perl space and to get the results in Perl Arrays and Hashes. The module's name is'P4', whilst 'P4Perl' is the product name. The reasons for this are complexand historical so just trust me on this one.'P4' is a Perl/XS extension brings the Perforce API into Perl space. It's object oriented and should be fairly intuitive for Perlusers. P4 used to depend on the P4::Client module, but all 3.x and later builds are completely independent and P4::Client is deprecated.LicenseP4Perl is distributed under the terms of this license, which is basically the BSD license. You use it at your own risk.Build RequirementsYou'll need a fairly recent Perl installed. P4Perl can be compiled to workwith any version of Perl (that I know of) from 5.005 onwards. That said,anyone still using 5.005 needs a nudge.P4 is C/C++ based and you need a C and C++ compiler on your machineto install it. The C++ compiler you use must be compatible with the compiler used by Perforce to build the Perforce API you're using. Mostlythis is a question of making sure you download the correct API! Before you can compile P4 successfully, you will need to download the Perforce API tarball separately from the Perforce FTP Site. The current version of P4Perl requires a 2004.2 API to build as itincludes support for 2004.2 API features. If you can't locate theright API build for your platform, [email protected] is not supported by Perforce Software. It is supportedby me, personally. So send all support requests to [email protected]. I'll deal with them as quickly as possible.Getting Started1. Get PerlLinux and FreeBSD users almost certainly already have Perl installed as it'sused by so many other packages. If you don't have it installed and youcan't find a binary package for your platform, then you can download thesource code from CPAN - the Comprehensive Perl Archive Network.For Windows users, ActivePerl is known to work with P4Perl and you don't need to do the build yourself.Once you have Perl installed, proceed to step 2.2. Get P4PerlI maintain a so called "stable" release of Perl for people who like to avoid using the latest builds. Those who are a little more adventurouscan use the current development build. Windows InstallersWindows users using ActivePerl can skip the rest and just download aWindows installer from the table below. Perl Version Installer Active Perl 5.6 (Build 633) Released (2.2596) Current Active Perl 5.8 (Build 804) Released (2.2596) Current Latest Sources Source Tarball Change log P4.tar.gz Changes Released Sources P4 Sources P4-Client Sources P4-1.4320.tar.gz(final 1.x release) P4-1.2587.tar.gz P4-1.1733.tar.gz Perl Production-ready, under active development Perl 5.40.1 is the current stable version of Perl. Perl is actively maintained and developed (git repository) by a large group of dedicated Perl Production-ready, under active development Perl 5.40.1 is the current stable version of Perl. Perl is actively maintained and developed (git repository) by a large group of dedicated With P4Perl and you don't need to do the build yourself.Once you have Perl installed, proceed to step 2.2. Get P4PerlI maintain a so called "stable" release of Perl for people who like to avoid using the latest builds. Those who are a little more adventurouscan use the current development build. Windows InstallersWindows users using ActivePerl can skip the rest and just download aWindows installer from the table below. Perl Version Installer Active Perl 5.6 (Build 633) Released (2.2596) Current Active Perl 5.8 (Build 804) Released (2.2596) Current Current Sources Source Tarball Change log P4-Client.tar.gz Changes P4.tar.gz Changes Released Sources P4-Client Sources P4 Sources P4-Client-2.2596.tar.gz (latest) P4-Client-2.2279.tar.gz P4-Client-1.1980.tar.gz P4-Client-1.1711.tar.gz P4-Client-1.1084.tar.gz P4-Client-1.977.tar.gz P4-Client-1.923.tar.gz P4-Client-0.52.tar.gz P4-Client-0.51.tar.gz P4-1.2587.tar.gz (latest) P4-1.1733.tar.gz (initial release) P4-0.982.tar.gz (beta build) 3. Get the Perforce APIGo to the Perforce Download Area and grab the latest available p4api.tar for your platform. If the latest release is not available, [email protected] as some APIbuilds are only done on request.Unpack the tarfile in a new, empty directory. You'll need it later.4. Build and Install P4PerlUnpack the P4-Client tarball and follow the build instructions in the READMEfile. Basically it comes down to the usual steps: perl Makefile.PL make make test make install(Windows users, use "nmake" instead of "make"). Now repeat the processfor the P4 tarball and once that's done, you can start using P4Perl.DocumentationDocumentation on how to use these extensions is in POD format within the distributions themselves. The docs from the head revision build are available as HTML here:P4:: DocumentationP4::Client DocumentationP4::UI DocumentationP4-Client Porting MatrixThe following porting combinations have been successfully built and tested and should compile without problems. Perl's build environment is not ideally suited to C++ extensions (or at least I haven't found a really good way of making it work with C++ extensions) so you building on other platforms may require some fiddling with the compiler rules. See hints/linux.pl and the PORTING file for hints on how to go about it.If you port P4-Client to another platform, please tell me how you did it so that we can make it available for other users. Platform Perl Versions Perforce API Versions (ifComments
P4Perl- Perl Extensions to the Perforce API IntroductionSo what's P4Perl about? In a nutshell P4Perl is the product name for a Perl module that allows you to execute Perforce commands without leaving Perl space and to get the results in Perl Arrays and Hashes. The module's name is'P4', whilst 'P4Perl' is the product name. The reasons for this are complexand historical so just trust me on this one.'P4' is a Perl/XS extension brings the Perforce API into Perl space. It's object oriented and should be fairly intuitive for Perlusers. P4 used to depend on the P4::Client module, but all 3.x and later builds are completely independent and P4::Client is deprecated.LicenseP4Perl is distributed under the terms of this license, which is basically the BSD license. You use it at your own risk.Build RequirementsYou'll need a fairly recent Perl installed. P4Perl can be compiled to workwith any version of Perl (that I know of) from 5.005 onwards. That said,anyone still using 5.005 needs a nudge.P4 is C/C++ based and you need a C and C++ compiler on your machineto install it. The C++ compiler you use must be compatible with the compiler used by Perforce to build the Perforce API you're using. Mostlythis is a question of making sure you download the correct API! Before you can compile P4 successfully, you will need to download the Perforce API tarball separately from the Perforce FTP Site. The current version of P4Perl requires a 2004.2 API to build as itincludes support for 2004.2 API features. If you can't locate theright API build for your platform, [email protected] is not supported by Perforce Software. It is supportedby me, personally. So send all support requests to [email protected]. I'll deal with them as quickly as possible.Getting Started1. Get PerlLinux and FreeBSD users almost certainly already have Perl installed as it'sused by so many other packages. If you don't have it installed and youcan't find a binary package for your platform, then you can download thesource code from CPAN - the Comprehensive Perl Archive Network.For Windows users, ActivePerl is known to work with P4Perl and you don't need to do the build yourself.Once you have Perl installed, proceed to step 2.2. Get P4PerlI maintain a so called "stable" release of Perl for people who like to avoid using the latest builds. Those who are a little more adventurouscan use the current development build. Windows InstallersWindows users using ActivePerl can skip the rest and just download aWindows installer from the table below. Perl Version Installer Active Perl 5.6 (Build 633) Released (2.2596) Current Active Perl 5.8 (Build 804) Released (2.2596) Current Latest Sources Source Tarball Change log P4.tar.gz Changes Released Sources P4 Sources P4-Client Sources P4-1.4320.tar.gz(final 1.x release) P4-1.2587.tar.gz P4-1.1733.tar.gz
2025-04-06With P4Perl and you don't need to do the build yourself.Once you have Perl installed, proceed to step 2.2. Get P4PerlI maintain a so called "stable" release of Perl for people who like to avoid using the latest builds. Those who are a little more adventurouscan use the current development build. Windows InstallersWindows users using ActivePerl can skip the rest and just download aWindows installer from the table below. Perl Version Installer Active Perl 5.6 (Build 633) Released (2.2596) Current Active Perl 5.8 (Build 804) Released (2.2596) Current Current Sources Source Tarball Change log P4-Client.tar.gz Changes P4.tar.gz Changes Released Sources P4-Client Sources P4 Sources P4-Client-2.2596.tar.gz (latest) P4-Client-2.2279.tar.gz P4-Client-1.1980.tar.gz P4-Client-1.1711.tar.gz P4-Client-1.1084.tar.gz P4-Client-1.977.tar.gz P4-Client-1.923.tar.gz P4-Client-0.52.tar.gz P4-Client-0.51.tar.gz P4-1.2587.tar.gz (latest) P4-1.1733.tar.gz (initial release) P4-0.982.tar.gz (beta build) 3. Get the Perforce APIGo to the Perforce Download Area and grab the latest available p4api.tar for your platform. If the latest release is not available, [email protected] as some APIbuilds are only done on request.Unpack the tarfile in a new, empty directory. You'll need it later.4. Build and Install P4PerlUnpack the P4-Client tarball and follow the build instructions in the READMEfile. Basically it comes down to the usual steps: perl Makefile.PL make make test make install(Windows users, use "nmake" instead of "make"). Now repeat the processfor the P4 tarball and once that's done, you can start using P4Perl.DocumentationDocumentation on how to use these extensions is in POD format within the distributions themselves. The docs from the head revision build are available as HTML here:P4:: DocumentationP4::Client DocumentationP4::UI DocumentationP4-Client Porting MatrixThe following porting combinations have been successfully built and tested and should compile without problems. Perl's build environment is not ideally suited to C++ extensions (or at least I haven't found a really good way of making it work with C++ extensions) so you building on other platforms may require some fiddling with the compiler rules. See hints/linux.pl and the PORTING file for hints on how to go about it.If you port P4-Client to another platform, please tell me how you did it so that we can make it available for other users. Platform Perl Versions Perforce API Versions (if
2025-04-20Hi,For Iwas trying to enable plperl on windows. And run into quite a few roadblocks -enough that I gave up.1) plperl doesn't build against a modern-ish perl. The fix for that seems easy enough: For some reason src/tools/install.pl doesn't install plperl[u].control, plperl[u]--1.0.sql - But apparently the buildfarm doesn't have that issue, because drongo successfully ran the plperl tests?3) When building against strawberry perl 5.32.1.1 I see errors when loading plperl4) When building against strawberry perl 5.30.3.1 I see a crash during execution of very simple statements [1]5) Finally when building against strawberry perl 5.28.2.1, plperl kinda works. But there's a lot of regression test failures, many of them seemingly around error trapping.I saw that there's also active state perl, but it seems to require clickingthrough some terms and conditions for every download that I don't want toagree to.Greetings,Andres Freund[1]Exception thrown at 0x000000006FD75DB8 (perl530.dll) in postgres.exe: 0xC0000005: Access violation reading location0x0000000000000008. perl530.dll!Perl_mg_get() + 56 bytes Unknown plperl.dll!select_perl_context(bool trusted) Line 667 C plperl.dll!plperl_inline_handler(FunctionCallInfoBaseData * fcinfo) Line 1941 C plperl.dll!plperlu_inline_handler(FunctionCallInfoBaseData * fcinfo) Line 2064 C postgres.exe!FunctionCall1Coll(FmgrInfo * flinfo, unsigned int collation, unsigned __int64 arg1) Line 1138 C postgres.exe!OidFunctionCall1Coll(unsigned int functionId, unsigned int collation, unsigned __int64 arg1) Line1417 C postgres.exe!ExecuteDoStmt(ParseState * pstate, DoStmt * stmt, bool atomic) Line 2146 C postgres.exe!standard_ProcessUtility(PlannedStmt * pstmt, const char * queryString, bool readOnlyTree,ProcessUtilityContextcontext, ParamListInfoData * params, QueryEnvironment * queryEnv, _DestReceiver * dest,QueryCompletion* qc) Line 712 C postgres.exe!ProcessUtility(PlannedStmt * pstmt, const char * queryString, bool readOnlyTree,ProcessUtilityContextcontext, ParamListInfoData * params, QueryEnvironment * queryEnv, _DestReceiver * dest,QueryCompletion* qc) Line 530 C
2025-04-09Change, standard Perl rather than Active Perl isused. #16 22297 C. Thomas Tyler Added DVCS environment isolation safety feature.Updated Perforce release to 2017.1.Bypassing pre-commit review to dev branch, as this is needed tofix a demo.#review-22298 #15 21962 C. Thomas Tyler Updated various scripts to use run() and rrun() functions in favorof predecessor runCmd() and runRemoteCmd(). The older functions won'tbe removed to avoid breaking scripts that rely on their behavior andhave no issues with them. The newer fuctions are more scalable andavoid erroneous "Argument list too long" from bash due to bufferoverruns when used with commands with large amounts of output.Enhanced runRemoteCmd() to clean up after itself, as it generated filesin /tmp that didn't get automatically cleaned up. If used in scriptscalled very often (e.g. every 5 minutes in a crontab), this leads tosignificant issues with /tmp filling up with garbage files over aperiod of several weeks.Enhanced test_utils.sh to test new run() and rrun() calls. #14 21549 C. Thomas Tyler Enhanced install_sdp_perl.sh v1.5.3:* Based on 2016.1 rather than 2014.1 P4API pulled from the Perforce FTP server.* Refactored to pull P4Perl 2016.1 from The WorkshopTested on CentOS 7: It works, using ActivePerl 5.24 and glibc 2.15.Tested on CentOS 6: It fails, due to dependency on glibc 2.14, whichrequires an older version of ActivePerl that is no longer freely availablefrom ActiveState. We need an older release of Perl (5.18?) to fix this;doesn't seem like it will be easy to acquire.Not tested on Ubuntu, but should work as Ubuntu prioritizes aggressiveadoption of shiny new things (rather than the stability-prioritizedslow adoption approach of CentOS), so the new glibc needed by thecurrently available Perl should be available.The earlier version of this script, which used to work, no longer works duedepending on an older version of ActivePerl that is also no longer freelyavailable.#review @paul_allen @sven_erik_knop #13 21214 C. Thomas Tyler Removed hard-coded reference to SDP instance 1 for temp files. #12 21177 C. Thomas Tyler Enhanced SDP Python installer to 'http:' protocol in place of'ftp:' in URL references. This works around a problem I encounteredwith outbound 'ftp' being blocked by some corporate firewall (not thelocal machine firewall). Using 'http:' in the URL works just as wellfor the purposes of this script.Enhanced SDP Perl installer in the same way, but the SDP Perl is brokennow for unrelated reasons. #11 20324 C. Thomas Tyler Corrected glibc version for Perl 5.24.0.2400. #10 20321 C. Thomas Tyler install_sdp_perl.sh v1.1.1:* Updated to
2025-04-01#1 Despite the endless errors in the configs and bugs in basic assembly, I'm trying to experiment with proxmox. This time I took the standalone image proxmox-ve_5.0-af4267bf-4.iso for testing. Make a cluster - pvecm create + pvecm add. It is not trouble. Ceph.pveceph install on each of 3 nodespveceph init --network x.x.x.x/24 on first nodepveceph createmon on eachTry to check it in GUI and get got timeout (500) on OSD page, even after making OSD from shell.In logs no info about that.P.S.: and I know. I'm a looser. #3 Hi I have the same problem, if I want to create OSD in GUI, PVE5 show me "got time out (500)"# ceph status cluster: id: ff5d73f9-b320-4a2b-bec9-0484ab192d20 health: HEALTH_OK services: mon: 3 daemons, quorum 0,1,2 mgr: no daemons active osd: 0 osds: 0 up, 0 in data: pools: 0 pools, 0 pgs objects: 0 objects, 0 bytes usage: 0 kB used, 0 kB / 0 kB avail pgs:Health status is OK but mgr: no daemons active.Any ideas? tom Proxmox Staff Member #4 ... mgr: no daemons active ... Create Ceph Manager (mgr) on each Monitor host.> pveceph createmgr #5 Command 'pveceph createmgr' it doesn't work:CLI show me: ERROR: unknown command 'createmgr'but I tested command from ceph manual:# ceph auth get-or-create mgr.$name mon 'allow profile mgr' osd 'allow *' mds 'allow *'# ceph-mgr -i $nameand also nothing, ceph status show me: mgr no deamons active.More ideas? tom Proxmox Staff Member #6 unknown command? seem you do not run latest packages, upgrade to latest and post your:> pveversion -v #7 I upgraded everything yesterday.# pveversion -vproxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)pve-kernel-4.10.15-1-pve: 4.10.15-15libpve-http-server-perl: 2.0-5lvm2: 2.02.168-pve2corosync: 2.4.2-pve3libqb0: 1.0.1-1pve-cluster: 5.0-10qemu-server: 5.0-12pve-firmware: 2.0-2libpve-common-perl: 5.0-16libpve-guest-common-perl: 2.0-11libpve-access-control: 5.0-5libpve-storage-perl: 5.0-12pve-libspice-server1: 0.12.8-3vncterm: 1.5-2pve-docs: 5.0-6pve-qemu-kvm: 2.9.0-2pve-container: 2.0-14pve-firewall: 3.0-1pve-ha-manager: 2.0-2ksm-control-daemon: 1.2-2glusterfs-client: 3.8.8-1lxc-pve: 2.0.8-3lxcfs: 2.0.7-pve2criu: 2.11.1-1~bpo90novnc-pve: 0.6-4smartmontools: 6.5+svn4324-1zfsutils-linux: 0.6.5.9-pve16~bpo90ceph: 12.1.2-pve1Today after apt update && apt dist-upgrade CLI show me:# apt update && apt dist-upgradeIgn:1 ......................../debian stretch InReleaseHit:2 .................................../debian stretch ReleaseHit:4 .........download.proxmox...../debian/ceph-luminous stretch InReleaseHit:5 ........security.debian... stretch/updates InReleaseIgn:6 ........enterprise.proxmox...../debian/pve stretch InReleaseErr:7 .........enterprise.proxmox...../debian/pve stretch Release 401 UnauthorizedReading package lists... DoneE: The repository '...........enterprise.proxmox...../debian/pve stretch Release' does not have a Release file.N: Updating from such a
2025-04-01Download PDFlib 10.0.3 The PDFlib download packages contain combined binaries for PDFlib, PDFlib+PDI, and PDFlib Personalization Server (PPS). Download the software package by clicking on the appropriate language binding for your platform. Refer to the corresponding system requirements document for deployment details.PDFlib, PDFlib+PDI, and PPS can be evaluated without a license, but display a demo stamp across all generated pages unless a valid license key is applied. With the purchase of a product license you will receive a license key. According to your purchase, the license key will activate PDFlib, PDFlib+PDI, or PPS, and will turn the software to an unrestricted version for commercial use.English PDFlib manuals are included in each of the packages. German and Japanese language manuals are available for download at the end of this page. Maintenance mode PDFlib 10 is in maintenance mode and will be maintained and supported until the end of the product lifetime (12/2027). However, PDFlib Product Family will no longer get any new features. Usability of Maintenance Releases The latest PDFlib 10 maintenance release is available to customers who purchase a new license and to customers with an active support agreement. Customers with a license for an older maintenance release can purchase a minor update to use the latest maintenance release. PDFlib / PDFlib+PDI / PDFlib Personalization Server (PPS) 10.0.3 (released 01/2025) Platform Package for use with Windows - see system requirements Windows Server x86 and Windows 10/11 x86 C, C++ Java Perl PHP1 Python Windows Server x64 and Windows 10/11 x64 C, C++ Java Perl PHP1 Python Ruby macOS - see system requirements Universal binary (x64/ARM64) for macOS 10.9 and above C, C++, Objective-C Java Perl PHP1 Python Ruby .NET Universal package - see system requirements Windows x86, Windows x64, Linux x64, Alpine Linux x64, macOS x64 all languages supported in .NET Linux - see system requirements Linux x64 C, C++ Java Perl PHP1 Python Ruby Alpine Linux x64 with musl C C, C++ Java Perl PHP1 Python Ruby Linux ARM64 (aarch64) C, C++ Java Perl PHP1 Python Ruby Linux on IBM System Z see below FreeBSD - see system requirements FreeBSD 12 x64 C, C++ Java Perl PHP1 Python Ruby IBM AIX - see system requirements IBM AIX 7.1 and above 64-bit C, C++ Java Python IBM System i and IBM System Z - see system requirements IBM System i 7.2 and above C, C++ Java2 RPG IBM System Z (USS, 64-bit) C, C++ Java IBM System Z (MVS) C Linux-S390x (64-bit) C, C++ Java 1) Please see the document PDFlib in PHP HowTo for details. 2) See here regarding the use of AIX binaries for Java for deployment on IBM System i.Supported versions of language bindings (not all versions are available on all platforms): PHP 8,1, 8.2, 8.3 and 8.4 Perl 5.30, 5.32, 5.34, 5.36, 5.38 and 5.40 Python 3.3 and newer Ruby 3.0 and above If you want to check that your download was free of transmission errors, we provide MD5 checksums for all download packages.See the change
2025-04-13