I agree with all these comments. There doesn't seem any need to rush it for 6.0, so that leaves time for polishing and resending after we're done with the release.
On 2016/07/08 06:53, Sebastien Marie wrote: > On Thu, Jul 07, 2016 at 06:18:07PM +0200, Solène wrote: > > > > Up > > > > What would be required to get the port imported ? I use it and actually I > > didn't had any error. > > > > Regards > > > > Despite the fact we will enter very soon in "slow motion" due to > locking, there are several things still required: > > - agreement of two devs for importing > > - a complete tgz for the port : your last sending needs adjustements. > > > Regarding enhancements for your submission: > > - you could based the initial work on portgen generated ports, and > improve them. > > - it means including p5-AWS-Signature4, p5-String-Escape, and > p5-Test-UseAllModules ports in the submission. > > - renaming p5-Rex to rex : ansible or salt doesn't have any prefix. > > - one point where I am a bit shared: reading the code, I am septical > if rex will work for targeting OpenBSD. I know it isn't your > use-case, but including a port in OpenBSD means the port should work > on OpenBSD (for targeting other OS or targeting OpenBSD). > > At least adding a big warning that the support of OpenBSD (as > target) isn't complete ? (I am just hoping that it just doesn't > work, and isn't harmful for the targeted system). > > Thanks. > -- > Sebastien Marie >