Perhaps patchfiles could take a path as a value? patchfiles patch-current.diff patchfiles patch-relative-to-filespath.diff patchfiles /why/would/we/want/this/patch-full-path.diff
I should have check first, does patchfiles already work this way? Regards, Bradley Giesbrecht (pixilla) > On Dec 15, 2015, at 4:02 PM, [email protected] wrote: > > Revision > 143621 <https://trac.macports.org/changeset/143621>Author > [email protected] <mailto:[email protected]>Date > 2015-12-15 16:02:40 -0800 (Tue, 15 Dec 2015) > Log Message > > perl5: allow patch file to be found in new file structure of r143612 > <https://trac.macports.org/changeset/143612> > Modified Paths > > trunk/dports/lang/perl5/Portfile <x-msg://44/#trunkdportslangperl5Portfile> > Diff > > <>Modified: trunk/dports/lang/perl5/Portfile (143620 => 143621) > > --- trunk/dports/lang/perl5/Portfile 2015-12-16 00:00:52 UTC (rev 143620) > +++ trunk/dports/lang/perl5/Portfile 2015-12-16 00:02:40 UTC (rev 143621) > @@ -121,7 +121,7 @@ > > if {[variant_isset universal]} { > post-configure { > - system "cd ${worksrcpath} && ed - ${worksrcpath}/config.h < > ${filespath}/config.h.ed" > + system "cd ${worksrcpath} && ed - ${worksrcpath}/config.h < > ${filespath}/${perl5.major}/config.h.ed" > } > } > > _______________________________________________ > macports-changes mailing list > [email protected] > <mailto:[email protected]> > https://lists.macosforge.org/mailman/listinfo/macports-changes > <https://lists.macosforge.org/mailman/listinfo/macports-changes>
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
