On Sat, Oct 20, 2018 at 08:15:18PM +0200, Charlene Wendling wrote: > Hi ports, > > ---- > Intro: > > I've worked on an update for all POE related ports (this includes > consumers), off by one because we would need a newer Perl [1]. You can > find the whole result on -wip or in the original repo [2].
Yay! Hopefully I'll get to #1 soonish, working on some ports stuff to get back into the swing of it after having to take a break. > For now i'm proposing only ports that can be committed individually, > i'll do another round with the ones that need to be commited in one > go. If you'd prefer another way to organise this, tell me. > > The whole update has been built with dpb on amd64 and i386 > successfully. There are only a few consumers to test against it sadly. > ---- > > So here is devel/p5-IO-Pipely, a Perl module that creates portable > pipes or pipe-like handles. It's needed for updating devel/p5-POE. > > WWW: https://metacpan.org/pod/IO::Pipely > > 'make test' runs without issues. > > Comments/feedbacks are welcome! As I'm sure bluhm@ would agree, it would be nice to see a MAINTAINER in the port, so if you don't mind. I would like to see explicitly setting the TEST_ENV so things that people have in their environment don't effect the test run. I tried it with this and it worked, although skipped the pod-coverage test as we don't have p5-Pod-Coverage-TrustPod, but no idea if we want to enable or disable RELEASE_TESTING. I tried TEST_ENV = RELEASE_TESTING=1 RUN_NETWORK_TESTS=0 Other than that, this looks OK to me, many thanks! > Charlène. > > > [1] https://marc.info/?l=openbsd-tech&m=153790876507733&w=2 > [2] https://github.com/julianaito/POE-ports -- andrew - http://afresh1.com Full-time system administration is a delicate balance between proactiveness and laziness. -- jhorwitz from use.perl.org
